Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 729d7bd369e81ef2acb2b7d77484f7aedabb4efdb973d4ed43deef4b97d223d3

Tx prefix hash: 582808717cafcdf49ae3c912bc8e3f3f02613878550f863ae3834e7de91e26b1
Tx public key: a3d64aebea6f7856af1a47d61e12dad14f5c0aecec7d09c3fbbd06a9d010c298
Timestamp: 1750840610 Timestamp [UCT]: 2025-06-25 08:36:50 Age [y:d:h:m:s]: 00:137:11:05:54
Block: 1312396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96187 RingCT/type: yes/0
Extra: 01a3d64aebea6f7856af1a47d61e12dad14f5c0aecec7d09c3fbbd06a9d010c29802110000001143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4971244ce34bdc4c2ad265a86d0491e6fe4592777dce79aee189edb66c194a8 0.600000000000 1800029 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": 1312406, "vin": [ { "gen": { "height": 1312396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4971244ce34bdc4c2ad265a86d0491e6fe4592777dce79aee189edb66c194a8" } } ], "extra": [ 1, 163, 214, 74, 235, 234, 111, 120, 86, 175, 26, 71, 214, 30, 18, 218, 209, 79, 92, 10, 236, 236, 125, 9, 195, 251, 189, 6, 169, 208, 16, 194, 152, 2, 17, 0, 0, 0, 17, 67, 132, 109, 102, 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