Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efc6215a55f27e897c05839d4b73069f4fc374c6fb19f0b832d9dcdfd04060c0

Tx prefix hash: 72f576f2f19831d0486cf4c569acf3d56584cd46e636a34fe18fa55d1fa43891
Tx public key: bf9babaea9db6c5458c3b0204269edfb049e5b07002e7ebd96dea54b970fc71a
Timestamp: 1720122445 Timestamp [UCT]: 2024-07-04 19:47:25 Age [y:d:h:m:s]: 00:171:10:39:18
Block: 1058561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122727 RingCT/type: yes/0
Extra: 01bf9babaea9db6c5458c3b0204269edfb049e5b07002e7ebd96dea54b970fc71a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a7ae8591781ade23d3da9917f9a8f24feb1b3d96172b515c5f8af680f4fc8da 0.600000000000 1529018 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": 1058571, "vin": [ { "gen": { "height": 1058561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a7ae8591781ade23d3da9917f9a8f24feb1b3d96172b515c5f8af680f4fc8da" } } ], "extra": [ 1, 191, 155, 171, 174, 169, 219, 108, 84, 88, 195, 176, 32, 66, 105, 237, 251, 4, 158, 91, 7, 0, 46, 126, 189, 150, 222, 165, 75, 151, 15, 199, 26, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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