Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 394dcebafe8568794ca7a59dfcb895682f786879fc5eba9ac41815f09c024f42

Tx prefix hash: 057a45291915aca8c8aba9f4dfc4411b3014fd1d7a412131c5e85efed43d87c9
Tx public key: 913e3bd5ab29bf6e771bf6727b4408b727ecd38ee4c4502aa8fb41aa6714ce87
Timestamp: 1753966469 Timestamp [UCT]: 2025-07-31 12:54:29 Age [y:d:h:m:s]: 00:118:00:35:11
Block: 1337338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83226 RingCT/type: yes/0
Extra: 01913e3bd5ab29bf6e771bf6727b4408b727ecd38ee4c4502aa8fb41aa6714ce87021100000009ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ea2913c9d74e79f78863bb6a3c1432e6b19423ac87e320f22ca20b312aa2a27 0.600000000000 1825143 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": 1337348, "vin": [ { "gen": { "height": 1337338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ea2913c9d74e79f78863bb6a3c1432e6b19423ac87e320f22ca20b312aa2a27" } } ], "extra": [ 1, 145, 62, 59, 213, 171, 41, 191, 110, 119, 27, 246, 114, 123, 68, 8, 183, 39, 236, 211, 142, 228, 196, 80, 42, 168, 251, 65, 170, 103, 20, 206, 135, 2, 17, 0, 0, 0, 9, 173, 121, 72, 208, 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