Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9df08b2d12a53b556e99fb15b0ca81c6bc910f6551014d566543708e3e1bce47

Tx prefix hash: bcd5f9d2e576bfe42e33d4cf70e3d752ccf0df8378b7dbf5601e228262b4281b
Tx public key: 074694de93b80be333821a74cb994ccde0ffde4188498a1f3dca9dc63f4e5520
Timestamp: 1714117522 Timestamp [UCT]: 2024-04-26 07:45:22 Age [y:d:h:m:s]: 01:195:11:29:58
Block: 1008789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398344 RingCT/type: yes/0
Extra: 01074694de93b80be333821a74cb994ccde0ffde4188498a1f3dca9dc63f4e552002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50618ca2684edaaef8c00cb7c22ef7a7ed9c5a2beec04586fa655601c24e7835 0.600000000000 1470267 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": 1008799, "vin": [ { "gen": { "height": 1008789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50618ca2684edaaef8c00cb7c22ef7a7ed9c5a2beec04586fa655601c24e7835" } } ], "extra": [ 1, 7, 70, 148, 222, 147, 184, 11, 227, 51, 130, 26, 116, 203, 153, 76, 205, 224, 255, 222, 65, 136, 73, 138, 31, 61, 202, 157, 198, 63, 78, 85, 32, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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