Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ec42ed53d6ee3c0c3ebd509d3652db00d154dddece7af96999e873f7e1528e83

Tx prefix hash: 64f7216276e4046b4a6490e0dba200b85fe3edbfbcdc22a3921d89a6ad9726a1
Tx public key: 908f9d9cabc5e2a51705d3b6ec7d03b7564d45e3b96a77ea77444139b918ceac
Timestamp: 1648460502 Timestamp [UCT]: 2022-03-28 09:41:42 Age [y:d:h:m:s]: 03:045:02:21:10
Block: 468128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 812452 RingCT/type: yes/0
Extra: 01908f9d9cabc5e2a51705d3b6ec7d03b7564d45e3b96a77ea77444139b918ceac021100000011a8c141c5000000000000000000

1 output(s) for total of 17.256150429000 dcy

stealth address amount amount idx
00: 2853762caa7532552d9c7187714a369ab8073a57c2ffcc8fc29b5fefab4db682 17.256150429000 886776 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 468138, "vin": [ { "gen": { "height": 468128 } } ], "vout": [ { "amount": 17256150429, "target": { "key": "2853762caa7532552d9c7187714a369ab8073a57c2ffcc8fc29b5fefab4db682" } } ], "extra": [ 1, 144, 143, 157, 156, 171, 197, 226, 165, 23, 5, 211, 182, 236, 125, 3, 183, 86, 77, 69, 227, 185, 106, 119, 234, 119, 68, 65, 57, 185, 24, 206, 172, 2, 17, 0, 0, 0, 17, 168, 193, 65, 197, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8