Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d8a1301694aa94528e39760da64b077a5f536f5ce951ff90476f67b9235ab3d

Tx prefix hash: e026d2d1d8c6b6736ff07ff57cf4a917252dfa37fbc0854571080205b2aeec4e
Tx public key: c9410871d8d5016a3fd1e4eba2c693e546fa0f1050b54fdd05a04828bc4cec54
Timestamp: 1759806691 Timestamp [UCT]: 2025-10-07 03:11:31 Age [y:d:h:m:s]: 00:077:21:05:50
Block: 1384447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55760 RingCT/type: yes/0
Extra: 01c9410871d8d5016a3fd1e4eba2c693e546fa0f1050b54fdd05a04828bc4cec5402110000000501491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7876554d0a41e53f2256d7cee2d0a75dd526386d81f3703f0c26cec7b34f0d3 0.600000000000 1872600 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": 1384457, "vin": [ { "gen": { "height": 1384447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7876554d0a41e53f2256d7cee2d0a75dd526386d81f3703f0c26cec7b34f0d3" } } ], "extra": [ 1, 201, 65, 8, 113, 216, 213, 1, 106, 63, 209, 228, 235, 162, 198, 147, 229, 70, 250, 15, 16, 80, 181, 79, 221, 5, 160, 72, 40, 188, 76, 236, 84, 2, 17, 0, 0, 0, 5, 1, 73, 31, 136, 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