Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d6823e19565e8e54bed84eb7243f7a039f63cbafbe98ea61f21dfea2a64339e

Tx prefix hash: 62633fbf77d3877895e30ce196c1ac85d7f8ace84bef6cb007e78e57ec9f63b1
Tx public key: 3e339019d35010bf4f5f8b2194404f9759d4d71dfef4ca85ca10b0d64084ef7f
Timestamp: 1747672735 Timestamp [UCT]: 2025-05-19 16:38:55 Age [y:d:h:m:s]: 00:184:15:22:34
Block: 1286440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129668 RingCT/type: yes/0
Extra: 013e339019d35010bf4f5f8b2194404f9759d4d71dfef4ca85ca10b0d64084ef7f0211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 797f3dfe70436922823741ceb0d6b08330e0f2d8e114d5d24972c3e6920c410c 0.600000000000 1773905 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": 1286450, "vin": [ { "gen": { "height": 1286440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "797f3dfe70436922823741ceb0d6b08330e0f2d8e114d5d24972c3e6920c410c" } } ], "extra": [ 1, 62, 51, 144, 25, 211, 80, 16, 191, 79, 95, 139, 33, 148, 64, 79, 151, 89, 212, 215, 29, 254, 244, 202, 133, 202, 16, 176, 214, 64, 132, 239, 127, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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