Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d4b16a165bb30408c77ea4e08ad97ee0be385d6f8131a76913a17d2d91ca750

Tx prefix hash: 7f36e0b204c5aaf10991f959ce02accec632698cd86a74d14611e81f69ed0551
Tx public key: ad5f0750e38b7d6e35e5b24a1d218395b92a2e08965e0a0baab0796de699daa3
Timestamp: 1759502424 Timestamp [UCT]: 2025-10-03 14:40:24 Age [y:d:h:m:s]: 00:037:07:24:51
Block: 1381930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26727 RingCT/type: yes/0
Extra: 01ad5f0750e38b7d6e35e5b24a1d218395b92a2e08965e0a0baab0796de699daa302110000000797baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32dbcc141731eace4b9fcd1a9ff82f70562bdb06cc4c3fad231712c3ec11e44d 0.600000000000 1870065 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": 1381940, "vin": [ { "gen": { "height": 1381930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32dbcc141731eace4b9fcd1a9ff82f70562bdb06cc4c3fad231712c3ec11e44d" } } ], "extra": [ 1, 173, 95, 7, 80, 227, 139, 125, 110, 53, 229, 178, 74, 29, 33, 131, 149, 185, 42, 46, 8, 150, 94, 10, 11, 170, 176, 121, 109, 230, 153, 218, 163, 2, 17, 0, 0, 0, 7, 151, 186, 249, 34, 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