Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0905bae4e00e21d198e1f1216553897c5d44cdc35f0b269d05910f73c491c976

Tx prefix hash: 8216adcfa829cb21e7a2f43db5d2de237144c4dfb8e6e14919eef089448ad2a9
Tx public key: 5d94db144c40f2e8e664de1e8ef1b4e9337dfe8f72a14b5e6b122427aac58b12
Timestamp: 1737296896 Timestamp [UCT]: 2025-01-19 14:28:16 Age [y:d:h:m:s]: 00:337:09:36:26
Block: 1200765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238731 RingCT/type: yes/0
Extra: 015d94db144c40f2e8e664de1e8ef1b4e9337dfe8f72a14b5e6b122427aac58b12021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1438abf93914b58aacac0146ef7f6a2370f9848b8c79b55c6e10be3e7ad9b907 0.600000000000 1687410 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": 1200775, "vin": [ { "gen": { "height": 1200765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1438abf93914b58aacac0146ef7f6a2370f9848b8c79b55c6e10be3e7ad9b907" } } ], "extra": [ 1, 93, 148, 219, 20, 76, 64, 242, 232, 230, 100, 222, 30, 142, 241, 180, 233, 51, 125, 254, 143, 114, 161, 75, 94, 107, 18, 36, 39, 170, 197, 139, 18, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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