Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbcf1ccf0a81fc4485e3d702288d723ebbef72b249dc3ed23e214a28b584dc9a

Tx prefix hash: 5542b02b96d9fe7e1301c9b3ce6716e2851b49f1fd008c75a25903f9b441aac7
Tx public key: 4d51de9d4a414773764f57f636136f0bec06750263f3a7195e8a1d40126f80fc
Timestamp: 1740652582 Timestamp [UCT]: 2025-02-27 10:36:22 Age [y:d:h:m:s]: 00:267:13:45:38
Block: 1228305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189002 RingCT/type: yes/0
Extra: 014d51de9d4a414773764f57f636136f0bec06750263f3a7195e8a1d40126f80fc02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 943ff1154c9dd6a9b64e496524aa9bf5846dd31ff16b61840eff1ae622b35e0e 0.600000000000 1715182 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": 1228315, "vin": [ { "gen": { "height": 1228305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "943ff1154c9dd6a9b64e496524aa9bf5846dd31ff16b61840eff1ae622b35e0e" } } ], "extra": [ 1, 77, 81, 222, 157, 74, 65, 71, 115, 118, 79, 87, 246, 54, 19, 111, 11, 236, 6, 117, 2, 99, 243, 167, 25, 94, 138, 29, 64, 18, 111, 128, 252, 2, 17, 0, 0, 0, 12, 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