Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dcefc7388c9aa59acfb8ccb4e3cc2fc1f499d139c139da618fbc4a80fb23773

Tx prefix hash: 8c2a5eebd5c835ef77cd67d14f75d029f3dcdd9caffeb328101089e8b2121f67
Tx public key: 017cd993f4ba89f35232de9231210a01f9bec58c53eb54d7a94c16d681dc1f49
Timestamp: 1716837599 Timestamp [UCT]: 2024-05-27 19:19:59 Age [y:d:h:m:s]: 00:156:18:05:36
Block: 1031347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112204 RingCT/type: yes/0
Extra: 01017cd993f4ba89f35232de9231210a01f9bec58c53eb54d7a94c16d681dc1f4902110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c64bccfceeec040e1f438a765eba3c64cd2acc6492685765328303ae82c4a2d0 0.600000000000 1499776 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": 1031357, "vin": [ { "gen": { "height": 1031347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c64bccfceeec040e1f438a765eba3c64cd2acc6492685765328303ae82c4a2d0" } } ], "extra": [ 1, 1, 124, 217, 147, 244, 186, 137, 243, 82, 50, 222, 146, 49, 33, 10, 1, 249, 190, 197, 140, 83, 235, 84, 215, 169, 76, 22, 214, 129, 220, 31, 73, 2, 17, 0, 0, 0, 10, 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