Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b6ab65df313bf7dc5ab7006fb173ccbf7d0370d0e417fe404ec4b0040e216b9

Tx prefix hash: 43d58c57c64663585f97624da9376cec44b45a39294459aaf7f658a2e90fe3d4
Tx public key: 956ee1a50aecf7b3eeae42b6153fd747bc0b44a989bb5bb189282b135584b1bc
Timestamp: 1747306905 Timestamp [UCT]: 2025-05-15 11:01:45 Age [y:d:h:m:s]: 00:178:11:03:30
Block: 1283415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125242 RingCT/type: yes/0
Extra: 01956ee1a50aecf7b3eeae42b6153fd747bc0b44a989bb5bb189282b135584b1bc02110000000c1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8289a312f26a48a6b21def606af9b06f849cc37152de8145e5be83261e2107a7 0.600000000000 1770834 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": 1283425, "vin": [ { "gen": { "height": 1283415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8289a312f26a48a6b21def606af9b06f849cc37152de8145e5be83261e2107a7" } } ], "extra": [ 1, 149, 110, 225, 165, 10, 236, 247, 179, 238, 174, 66, 182, 21, 63, 215, 71, 188, 11, 68, 169, 137, 187, 91, 177, 137, 40, 43, 19, 85, 132, 177, 188, 2, 17, 0, 0, 0, 12, 31, 144, 81, 122, 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