Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81d3c3f09acc78ffbee9d9d8ead57308a3084dc6be695b1635370ce28caf6af8

Tx prefix hash: 98185f863e3257637832df2618c8ca7332f526ff5cb676ee481ea94a3c3bba45
Tx public key: 2ab1afdee8deb6d271cbcb76eaa6b243ce124570de48a6bd1ca11a3a052b9610
Timestamp: 1735920241 Timestamp [UCT]: 2025-01-03 16:04:01 Age [y:d:h:m:s]: 00:171:14:04:37
Block: 1189417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122211 RingCT/type: yes/0
Extra: 012ab1afdee8deb6d271cbcb76eaa6b243ce124570de48a6bd1ca11a3a052b96100211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0502fab6936b4146f114cdc30182c3947beb94d0e80a2a09dafad0873cf8fe15 0.600000000000 1675926 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": 1189427, "vin": [ { "gen": { "height": 1189417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0502fab6936b4146f114cdc30182c3947beb94d0e80a2a09dafad0873cf8fe15" } } ], "extra": [ 1, 42, 177, 175, 222, 232, 222, 182, 210, 113, 203, 203, 118, 234, 166, 178, 67, 206, 18, 69, 112, 222, 72, 166, 189, 28, 161, 26, 58, 5, 43, 150, 16, 2, 17, 0, 0, 0, 8, 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