Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9908a1d8236dc8093011ee1a5a7c7481e6d38ce99e6604c9edb0505905fd65f

Tx prefix hash: ee74772513c9597bc2e3594374cc340e7490299064b68dd55292a5fbf280caaa
Tx public key: d932a2735d1a02944d9c938e91e42135be360a0c7f340097a9599dc8eef09b41
Timestamp: 1728668877 Timestamp [UCT]: 2024-10-11 17:47:57 Age [y:d:h:m:s]: 01:052:19:27:04
Block: 1129428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296163 RingCT/type: yes/0
Extra: 01d932a2735d1a02944d9c938e91e42135be360a0c7f340097a9599dc8eef09b41021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa902e6165a175e92ead68151a74e25cebc9e13a0d6a2d8b8b3ddc3d3002fec2 0.600000000000 1612255 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": 1129438, "vin": [ { "gen": { "height": 1129428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa902e6165a175e92ead68151a74e25cebc9e13a0d6a2d8b8b3ddc3d3002fec2" } } ], "extra": [ 1, 217, 50, 162, 115, 93, 26, 2, 148, 77, 156, 147, 142, 145, 228, 33, 53, 190, 54, 10, 12, 127, 52, 0, 151, 169, 89, 157, 200, 238, 240, 155, 65, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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