Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 996b3a4abff9a55c33602681d87cccce9e6ba9c46e8806184a9a0caf5109e97a

Tx prefix hash: 03c6e186f0d7b4538d9618fff90a98f3306b9aa209d0d0f16e74c7ebfa7f9210
Tx public key: e3b87eef836ad35211b7b42fc6703319c2184d7103c7dc2646e99c64dac8f0f2
Timestamp: 1576424476 Timestamp [UCT]: 2019-12-15 15:41:16 Age [y:d:h:m:s]: 05:090:15:23:11
Block: 27379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1211574 RingCT/type: yes/0
Extra: 01e3b87eef836ad35211b7b42fc6703319c2184d7103c7dc2646e99c64dac8f0f202110000000dad433a0b000000000000000000

1 output(s) for total of 498.061386878000 dcy

stealth address amount amount idx
00: 6cd8a2d6ef413da68080354efb3746299212d618e6c1e69c6c2a42cc6c3bc285 498.061386878000 45375 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": 27389, "vin": [ { "gen": { "height": 27379 } } ], "vout": [ { "amount": 498061386878, "target": { "key": "6cd8a2d6ef413da68080354efb3746299212d618e6c1e69c6c2a42cc6c3bc285" } } ], "extra": [ 1, 227, 184, 126, 239, 131, 106, 211, 82, 17, 183, 180, 47, 198, 112, 51, 25, 194, 24, 77, 113, 3, 199, 220, 38, 70, 233, 156, 100, 218, 200, 240, 242, 2, 17, 0, 0, 0, 13, 173, 67, 58, 11, 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