Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c04f4da88497451c3ec7113e7472845d3bec4f7b59704ca0bfaa69c7e2be4620

Tx prefix hash: d8fc06f6373a0ac99935478e0ce5919a079ef76c2d5e7c60cee3e0c08a3d8445
Tx public key: 8158ce533daf0b4217d7a3377943c55b234eeeb26cf62e8c7f03f97f61fcd436
Timestamp: 1735145638 Timestamp [UCT]: 2024-12-25 16:53:58 Age [y:d:h:m:s]: 00:098:10:38:41
Block: 1183005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70125 RingCT/type: yes/0
Extra: 018158ce533daf0b4217d7a3377943c55b234eeeb26cf62e8c7f03f97f61fcd436021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ab6523ab1ac65c5dc3b1409e89f186c4b6a08bdb59bd5599ac95285b2ed9c53 0.600000000000 1669444 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": 1183015, "vin": [ { "gen": { "height": 1183005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ab6523ab1ac65c5dc3b1409e89f186c4b6a08bdb59bd5599ac95285b2ed9c53" } } ], "extra": [ 1, 129, 88, 206, 83, 61, 175, 11, 66, 23, 215, 163, 55, 121, 67, 197, 91, 35, 78, 238, 178, 108, 246, 46, 140, 127, 3, 249, 127, 97, 252, 212, 54, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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