Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34bd809240cee7e8902c1c089ff80d9e819a10ca7dd977637d401cd20ab14877

Tx prefix hash: b6ed0946133a0fa4a1faf7e9f1ef1308c05c5b9b06cf8575a25887b511f9fabd
Tx public key: ab1b9f7626aaf170d318a772d73e11f2d3acd69c12fd0bb3c33dd133019fefd1
Timestamp: 1745439245 Timestamp [UCT]: 2025-04-23 20:14:05 Age [y:d:h:m:s]: 00:017:21:09:04
Block: 1267940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12796 RingCT/type: yes/0
Extra: 01ab1b9f7626aaf170d318a772d73e11f2d3acd69c12fd0bb3c33dd133019fefd102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6dcec58d770baffd2a4d0a14d540108e167f6df06188457646a36362091b204 0.600000000000 1755169 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": 1267950, "vin": [ { "gen": { "height": 1267940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6dcec58d770baffd2a4d0a14d540108e167f6df06188457646a36362091b204" } } ], "extra": [ 1, 171, 27, 159, 118, 38, 170, 241, 112, 211, 24, 167, 114, 215, 62, 17, 242, 211, 172, 214, 156, 18, 253, 11, 179, 195, 61, 209, 51, 1, 159, 239, 209, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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