Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c76a2e5230e4837c89cc638e559c4757eff2b635966ce2e8fb0e61f3319f89e3

Tx prefix hash: 870cd9e052e47e5f9ce0b6d2659f65c01ec0ce8bf065ead8f12fa863e136563a
Tx public key: 5c7698154f1a0a63d3cf565f7ddc863ebb0fb283e4c35cd15fec791af559a30e
Timestamp: 1762024290 Timestamp [UCT]: 2025-11-01 19:11:30 Age [y:d:h:m:s]: 00:005:06:31:59
Block: 1402844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3758 RingCT/type: yes/0
Extra: 015c7698154f1a0a63d3cf565f7ddc863ebb0fb283e4c35cd15fec791af559a30e02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 969d5ba0a2de8c83daedd0b209a9d2f941ab0d16bfaaf3333c6098d2e5d020b1 0.600000000000 1891167 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": 1402854, "vin": [ { "gen": { "height": 1402844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "969d5ba0a2de8c83daedd0b209a9d2f941ab0d16bfaaf3333c6098d2e5d020b1" } } ], "extra": [ 1, 92, 118, 152, 21, 79, 26, 10, 99, 211, 207, 86, 95, 125, 220, 134, 62, 187, 15, 178, 131, 228, 195, 92, 209, 95, 236, 121, 26, 245, 89, 163, 14, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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