Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cece0e0b76a8dbf838d3c07dab3f46d43b4162952e3d4ec26bc049ebcbd85c6

Tx prefix hash: bb4555348863535cc1691a4ba3f7c5f6c3d76d4920ac27887ae995a30ea47165
Tx public key: 54bd04c05a0e516de1118453b02f434a2a9a2fa806fe0fc0aef0a3cd7225e760
Timestamp: 1738527500 Timestamp [UCT]: 2025-02-02 20:18:20 Age [y:d:h:m:s]: 00:334:14:03:45
Block: 1210718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236974 RingCT/type: yes/0
Extra: 0154bd04c05a0e516de1118453b02f434a2a9a2fa806fe0fc0aef0a3cd7225e760021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57816190beb80225f73e2aedb4a5c4fe534d1e49309d07a8176170ab6476092e 0.600000000000 1697473 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": 1210728, "vin": [ { "gen": { "height": 1210718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57816190beb80225f73e2aedb4a5c4fe534d1e49309d07a8176170ab6476092e" } } ], "extra": [ 1, 84, 189, 4, 192, 90, 14, 81, 109, 225, 17, 132, 83, 176, 47, 67, 74, 42, 154, 47, 168, 6, 254, 15, 192, 174, 240, 163, 205, 114, 37, 231, 96, 2, 17, 0, 0, 0, 3, 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