Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abae23c14b16a93b8eec221eafd30ed56afbecd6a4e050407472b2f7417219ba

Tx prefix hash: cb6ef6dc7464b6ae48ec7f58c4873e82693da65305388f5d4395fe37b5d85ef1
Tx public key: e97c064559d20e458c79e3aa24205cef0e7d311cad15ae3d4cb67ef9277429b2
Timestamp: 1722214859 Timestamp [UCT]: 2024-07-29 01:00:59 Age [y:d:h:m:s]: 00:263:04:09:40
Block: 1075913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188006 RingCT/type: yes/0
Extra: 01e97c064559d20e458c79e3aa24205cef0e7d311cad15ae3d4cb67ef9277429b202110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38269b0f1cc37783b6ce03c301209435e6510c764bdb0139be39bffaf35e8fc4 0.600000000000 1548444 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": 1075923, "vin": [ { "gen": { "height": 1075913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38269b0f1cc37783b6ce03c301209435e6510c764bdb0139be39bffaf35e8fc4" } } ], "extra": [ 1, 233, 124, 6, 69, 89, 210, 14, 69, 140, 121, 227, 170, 36, 32, 92, 239, 14, 125, 49, 28, 173, 21, 174, 61, 76, 182, 126, 249, 39, 116, 41, 178, 2, 17, 0, 0, 0, 11, 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