Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 826d321ce913835abac98c5314dfa6982132bb9bec8d036040152cb10a9050a9

Tx prefix hash: 8681e8446e318b51f92afd7a99b1ed839c3128a4d1db99a264f04481c1e19a0e
Tx public key: 32ca0e21c23d987fe934b3cdfe5e504e9c22ae0c713a996a05ed9842a606960a
Timestamp: 1736437437 Timestamp [UCT]: 2025-01-09 15:43:57 Age [y:d:h:m:s]: 00:159:15:56:41
Block: 1193692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113815 RingCT/type: yes/0
Extra: 0132ca0e21c23d987fe934b3cdfe5e504e9c22ae0c713a996a05ed9842a606960a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600060000000 dcy

stealth address amount amount idx
00: ec04f9a14535870c93039ef23dcbf8af95ae816cb873c48e9ff1c6bdb65214b5 0.600060000000 1680255 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": 1193702, "vin": [ { "gen": { "height": 1193692 } } ], "vout": [ { "amount": 600060000, "target": { "key": "ec04f9a14535870c93039ef23dcbf8af95ae816cb873c48e9ff1c6bdb65214b5" } } ], "extra": [ 1, 50, 202, 14, 33, 194, 61, 152, 127, 233, 52, 179, 205, 254, 94, 80, 78, 156, 34, 174, 12, 113, 58, 153, 106, 5, 237, 152, 66, 166, 6, 150, 10, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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