Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60693b388afe7ed035ec3abf05818d2cfc195b410fd5939be786499f6d062256

Tx prefix hash: 7bc4bc730c05fc58ba352132d94a9ce7452ecb1d54ff8b93753bc3f612e66ff6
Tx public key: fce403550bfc008167e3cbee8a38f6e5d6a5c77c8a56b07ff93fc396dcb286fe
Timestamp: 1583346558 Timestamp [UCT]: 2020-03-04 18:29:18 Age [y:d:h:m:s]: 04:256:17:02:38
Block: 76417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1077797 RingCT/type: yes/0
Extra: 01fce403550bfc008167e3cbee8a38f6e5d6a5c77c8a56b07ff93fc396dcb286fe02110000003c56c366d3000000000000000000

1 output(s) for total of 342.609619059000 dcy

stealth address amount amount idx
00: 88346a28bcefa26d42bb07df95fb0b46d68266fd0a153c2718c0061412e5efaf 342.609619059000 140667 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": 76427, "vin": [ { "gen": { "height": 76417 } } ], "vout": [ { "amount": 342609619059, "target": { "key": "88346a28bcefa26d42bb07df95fb0b46d68266fd0a153c2718c0061412e5efaf" } } ], "extra": [ 1, 252, 228, 3, 85, 11, 252, 0, 129, 103, 227, 203, 238, 138, 56, 246, 229, 214, 165, 199, 124, 138, 86, 176, 127, 249, 63, 195, 150, 220, 178, 134, 254, 2, 17, 0, 0, 0, 60, 86, 195, 102, 211, 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