Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344fb9abd1603e446194ae4c1c6a75c09d0bb42264a2ce196aa9cec8c57a94d5

Tx prefix hash: a7e924f39ef5ca7ffd69f73c9c09391cc47af3e800b41fd9952f31af3caca408
Tx public key: d1792f65c3277eb96be5c817947d5836220cf6b4c4ae9861d1dc016e70009110
Timestamp: 1730153385 Timestamp [UCT]: 2024-10-28 22:09:45 Age [y:d:h:m:s]: 00:157:18:41:52
Block: 1141663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112592 RingCT/type: yes/0
Extra: 01d1792f65c3277eb96be5c817947d5836220cf6b4c4ae9861d1dc016e70009110021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caaf338c39e5ff876b995054cf80bc3278f30f6e5054d35d9fb572295967aa61 0.600000000000 1625474 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": 1141673, "vin": [ { "gen": { "height": 1141663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caaf338c39e5ff876b995054cf80bc3278f30f6e5054d35d9fb572295967aa61" } } ], "extra": [ 1, 209, 121, 47, 101, 195, 39, 126, 185, 107, 229, 200, 23, 148, 125, 88, 54, 34, 12, 246, 180, 196, 174, 152, 97, 209, 220, 1, 110, 112, 0, 145, 16, 2, 17, 0, 0, 0, 4, 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