Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d70d8ce8738b2e894f4311e1ac7623926764884303e6bfb970ba101dad10dcd

Tx prefix hash: 141c90535ae28a2de6dfe0ca7999654a8199b42ee1e4b55eac62e5b7bc6d9b13
Tx public key: bd5e0e9b5a936b72f24ac88ac141a023dc4517caae58eb20aa1058c4a6580bd4
Timestamp: 1761880233 Timestamp [UCT]: 2025-10-31 03:10:33 Age [y:d:h:m:s]: 00:011:10:19:13
Block: 1401658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8169 RingCT/type: yes/0
Extra: 01bd5e0e9b5a936b72f24ac88ac141a023dc4517caae58eb20aa1058c4a6580bd40211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77a7df2f5e66f568445307b82f55e7b73845925c0fa75a840f64240fa72ec18b 0.600000000000 1889977 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": 1401668, "vin": [ { "gen": { "height": 1401658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77a7df2f5e66f568445307b82f55e7b73845925c0fa75a840f64240fa72ec18b" } } ], "extra": [ 1, 189, 94, 14, 155, 90, 147, 107, 114, 242, 74, 200, 138, 193, 65, 160, 35, 220, 69, 23, 202, 174, 88, 235, 32, 170, 16, 88, 196, 166, 88, 11, 212, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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