Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b52c8f9b8160a479c74f91b3be3123084f812d4528d7c4d0634bec33ab07fb7

Tx prefix hash: 8efb2da24287885fe26c4215d22d830fa28ce8d5abead4872fc8d8d273f26958
Tx public key: 112a8d9d81d8b582f9d6b8d581936bfba2db899acaac3a16726ec83d41f9f3ba
Timestamp: 1749868427 Timestamp [UCT]: 2025-06-14 02:33:47 Age [y:d:h:m:s]: 00:160:10:45:51
Block: 1304536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112429 RingCT/type: yes/0
Extra: 01112a8d9d81d8b582f9d6b8d581936bfba2db899acaac3a16726ec83d41f9f3ba0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38ea21d1e4fab837db75a15ff830475b0e6d5d7aaac864b27f0695bb4395bedd 0.600000000000 1792127 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": 1304546, "vin": [ { "gen": { "height": 1304536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38ea21d1e4fab837db75a15ff830475b0e6d5d7aaac864b27f0695bb4395bedd" } } ], "extra": [ 1, 17, 42, 141, 157, 129, 216, 181, 130, 249, 214, 184, 213, 129, 147, 107, 251, 162, 219, 137, 154, 202, 172, 58, 22, 114, 110, 200, 61, 65, 249, 243, 186, 2, 17, 0, 0, 0, 3, 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