Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f99f0adf88e513842611c2719e3b79bcc8eac593051d470747b4bdfa35e8cbbf

Tx prefix hash: debe80b5095e1224ae68fdfe793f76e9f2760485c7b4028650d8a916ad84017d
Tx public key: 57614c05abcf7045d9e1bef3a3689a62dac57bb42896daf561f18a1648d63a08
Timestamp: 1576927374 Timestamp [UCT]: 2019-12-21 11:22:54 Age [y:d:h:m:s]: 05:156:23:03:40
Block: 28962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1261596 RingCT/type: yes/0
Extra: 0157614c05abcf7045d9e1bef3a3689a62dac57bb42896daf561f18a1648d63a080211000000579159db1e000000000000000000

1 output(s) for total of 492.082290016000 dcy

stealth address amount amount idx
00: 35d20ad81c06c177bb5bb564a606d8d4c8f93f52b88cddc6da4baa15579e5b44 492.082290016000 47782 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": 28972, "vin": [ { "gen": { "height": 28962 } } ], "vout": [ { "amount": 492082290016, "target": { "key": "35d20ad81c06c177bb5bb564a606d8d4c8f93f52b88cddc6da4baa15579e5b44" } } ], "extra": [ 1, 87, 97, 76, 5, 171, 207, 112, 69, 217, 225, 190, 243, 163, 104, 154, 98, 218, 197, 123, 180, 40, 150, 218, 245, 97, 241, 138, 22, 72, 214, 58, 8, 2, 17, 0, 0, 0, 87, 145, 89, 219, 30, 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