Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 470467a98930d6d962c52e7484846e5c3fa590586bb21eae80a2079e7bb3d594

Tx prefix hash: 9a9c6bd60ce431a151861166705cd1a1943416c130a6242cbaa9e7f8a169df47
Tx public key: e52292173a49b432dad4eba44d862a3a4684e3a2839dc3a00f8594e0bbdfbf38
Timestamp: 1728610474 Timestamp [UCT]: 2024-10-11 01:34:34 Age [y:d:h:m:s]: 00:104:20:48:33
Block: 1128937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74923 RingCT/type: yes/0
Extra: 01e52292173a49b432dad4eba44d862a3a4684e3a2839dc3a00f8594e0bbdfbf3802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3d04c444789cf045c642aea5f345a045c75229a41f1f6bbddf87223c9c8539e 0.600000000000 1611760 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": 1128947, "vin": [ { "gen": { "height": 1128937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3d04c444789cf045c642aea5f345a045c75229a41f1f6bbddf87223c9c8539e" } } ], "extra": [ 1, 229, 34, 146, 23, 58, 73, 180, 50, 218, 212, 235, 164, 77, 134, 42, 58, 70, 132, 227, 162, 131, 157, 195, 160, 15, 133, 148, 224, 187, 223, 191, 56, 2, 17, 0, 0, 0, 7, 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