Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6162594e9f2f6c056526faddaa89bbab78a863956e3eb718debb339f0e52d59

Tx prefix hash: 24b7a98805eb5f9ad7d0be4fd3d98251577f16c1e88b6aa1004b977d01e7ccb4
Tx public key: 431fbf001c652f16c47345de0f87fb19ad8a6b94f1478dbd29bde0f48fdd737d
Timestamp: 1727726666 Timestamp [UCT]: 2024-09-30 20:04:26 Age [y:d:h:m:s]: 00:187:08:20:05
Block: 1121618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133695 RingCT/type: yes/0
Extra: 01431fbf001c652f16c47345de0f87fb19ad8a6b94f1478dbd29bde0f48fdd737d02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00b42a4e197e4fecae8a0a4edfa6a2662756ddd48e2167f9aba4ffbffaa1cd17 0.600000000000 1603921 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": 1121628, "vin": [ { "gen": { "height": 1121618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00b42a4e197e4fecae8a0a4edfa6a2662756ddd48e2167f9aba4ffbffaa1cd17" } } ], "extra": [ 1, 67, 31, 191, 0, 28, 101, 47, 22, 196, 115, 69, 222, 15, 135, 251, 25, 173, 138, 107, 148, 241, 71, 141, 189, 41, 189, 224, 244, 143, 221, 115, 125, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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