Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5301da09cf36d403debb3bdac3a2f1885e075ffcfc7d6cc74083fea4cbfa2f2

Tx prefix hash: 4713d4dac6567343bd4ec455914062d4bd77337d39b3da0023fba27505c751ed
Tx public key: 2deb3df03f8bc6a28db23125322d571e8805870ced63b5ad3ba099fce846d4b6
Timestamp: 1725018117 Timestamp [UCT]: 2024-08-30 11:41:57 Age [y:d:h:m:s]: 01:068:20:08:27
Block: 1099158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307636 RingCT/type: yes/0
Extra: 012deb3df03f8bc6a28db23125322d571e8805870ced63b5ad3ba099fce846d4b602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 565f3aed2e285f60fe46fed67cfa0bc9bee2b90a585efe9abcc4d2e22cdd3b6d 0.600000000000 1575085 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": 1099168, "vin": [ { "gen": { "height": 1099158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "565f3aed2e285f60fe46fed67cfa0bc9bee2b90a585efe9abcc4d2e22cdd3b6d" } } ], "extra": [ 1, 45, 235, 61, 240, 63, 139, 198, 162, 141, 178, 49, 37, 50, 45, 87, 30, 136, 5, 135, 12, 237, 99, 181, 173, 59, 160, 153, 252, 232, 70, 212, 182, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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