Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 349d5ee30db1fe6243b21df60a003881f9cd476ca7912f4f5f316813f5a0a506

Tx prefix hash: b6de0decaf32c9ad9b52fded51dad587fbefb7647b45af9e1dc0fc1e28794ed8
Tx public key: 7b476f9245a0956f863da62240028adb223a1af357e3a7c876f73fce9f0de0ee
Timestamp: 1751925964 Timestamp [UCT]: 2025-07-07 22:06:04 Age [y:d:h:m:s]: 00:209:15:45:02
Block: 1320887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148203 RingCT/type: yes/0
Extra: 017b476f9245a0956f863da62240028adb223a1af357e3a7c876f73fce9f0de0ee02110000000cbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bceffdda6193a0bd2bfec94cbab7a5454d09dee1bbb61d1bc8a4ebbc14f9c0b 0.600000000000 1808588 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": 1320897, "vin": [ { "gen": { "height": 1320887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bceffdda6193a0bd2bfec94cbab7a5454d09dee1bbb61d1bc8a4ebbc14f9c0b" } } ], "extra": [ 1, 123, 71, 111, 146, 69, 160, 149, 111, 134, 61, 166, 34, 64, 2, 138, 219, 34, 58, 26, 243, 87, 227, 167, 200, 118, 247, 63, 206, 159, 13, 224, 238, 2, 17, 0, 0, 0, 12, 191, 81, 178, 162, 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