Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42bbc2d9dab4fc56c9d5ba7b9e03a12618102a0cacb8c63aa9924fd7f32a45a9

Tx prefix hash: a2b517e0137169cabc4e579d1fe4a8c11947deea3e1e3b9edce9a2da862e8952
Tx public key: 65574677735e23aace591fa29ff65414947636cfc473f74bd97fc0072a1c7a2e
Timestamp: 1756052190 Timestamp [UCT]: 2025-08-24 16:16:30 Age [y:d:h:m:s]: 00:093:22:34:41
Block: 1353526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67078 RingCT/type: yes/0
Extra: 0165574677735e23aace591fa29ff65414947636cfc473f74bd97fc0072a1c7a2e0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9250048e056fb7c9370ae60e6fd4b0a7a09ad9f076603af1ca510b497da4dba 0.600000000000 1841501 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": 1353536, "vin": [ { "gen": { "height": 1353526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9250048e056fb7c9370ae60e6fd4b0a7a09ad9f076603af1ca510b497da4dba" } } ], "extra": [ 1, 101, 87, 70, 119, 115, 94, 35, 170, 206, 89, 31, 162, 159, 246, 84, 20, 148, 118, 54, 207, 196, 115, 247, 75, 217, 127, 192, 7, 42, 28, 122, 46, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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