Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2ec31347913b1fb06ba45d221ffe3401d9545826e85c64bdc16d69c32a57264

Tx prefix hash: 7653cdc54fea217fb2d3d337b54d580ced3e253e5576a1d5ef08386881b3abee
Tx public key: 09b3fb61556078b533b763354b35567823a29b74ae43b30213e22c4dd388b1e8
Timestamp: 1736106753 Timestamp [UCT]: 2025-01-05 19:52:33 Age [y:d:h:m:s]: 00:345:00:13:12
Block: 1190957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244113 RingCT/type: yes/0
Extra: 0109b3fb61556078b533b763354b35567823a29b74ae43b30213e22c4dd388b1e80211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5352c3527a7f647e3c9675c3a720a936fa0916562ee7bbae7a7e0f02e39ca777 0.600000000000 1677480 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": 1190967, "vin": [ { "gen": { "height": 1190957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5352c3527a7f647e3c9675c3a720a936fa0916562ee7bbae7a7e0f02e39ca777" } } ], "extra": [ 1, 9, 179, 251, 97, 85, 96, 120, 181, 51, 183, 99, 53, 75, 53, 86, 120, 35, 162, 155, 116, 174, 67, 179, 2, 19, 226, 44, 77, 211, 136, 177, 232, 2, 17, 0, 0, 0, 6, 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