Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25863988c2a2f87370ecf73801b1a5058b4e5a70409f3bc6442b832e75067a7b

Tx prefix hash: 78983fd0d75bc4cc80ec6774d2b3116d092d4ccecb75c83f9429180f3a676ede
Tx public key: 3b4011a81a7104e7b24de0df0c17a3bb5bccf5446ff626b1dbb03483072d8578
Timestamp: 1723404605 Timestamp [UCT]: 2024-08-11 19:30:05 Age [y:d:h:m:s]: 00:261:20:24:39
Block: 1085780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187039 RingCT/type: yes/0
Extra: 013b4011a81a7104e7b24de0df0c17a3bb5bccf5446ff626b1dbb03483072d8578021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fa668baafe3f5163e6f672b7b3223da5e42a5deb99f864fd1935e73a2f2396c 0.600000000000 1560369 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": 1085790, "vin": [ { "gen": { "height": 1085780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fa668baafe3f5163e6f672b7b3223da5e42a5deb99f864fd1935e73a2f2396c" } } ], "extra": [ 1, 59, 64, 17, 168, 26, 113, 4, 231, 178, 77, 224, 223, 12, 23, 163, 187, 91, 204, 245, 68, 111, 246, 38, 177, 219, 176, 52, 131, 7, 45, 133, 120, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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