Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a865c490c30a0db8662fbeb9d20cebaaa22ba8ba9fde8e34d0c2039632caa18

Tx prefix hash: baf6259adc3cb2b8ab78876808ec43e5b120dec9eccec139fda2d6b2359bd42f
Tx public key: 76d0cacb7b16866d3b681526d6c221a8fb11ef8ea652c331774dd06d3e025dd7
Timestamp: 1736901914 Timestamp [UCT]: 2025-01-15 00:45:14 Age [y:d:h:m:s]: 00:304:10:27:22
Block: 1197535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215083 RingCT/type: yes/0
Extra: 0176d0cacb7b16866d3b681526d6c221a8fb11ef8ea652c331774dd06d3e025dd702110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9b9e4b85489ad30bd979cec567372be96efe8cf9bf21533d44a9a648fad6190 0.600000000000 1684146 of 15

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": 1197545, "vin": [ { "gen": { "height": 1197535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9b9e4b85489ad30bd979cec567372be96efe8cf9bf21533d44a9a648fad6190" } } ], "extra": [ 1, 118, 208, 202, 203, 123, 22, 134, 109, 59, 104, 21, 38, 214, 194, 33, 168, 251, 17, 239, 142, 166, 82, 195, 49, 119, 77, 208, 109, 62, 2, 93, 215, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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