Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6571ceca77cd7bb8e28cfa4207742b3748c35087f3c40c1b4f2d0d32764c3c31

Tx prefix hash: 2261750d2b697af8d0bf3e62d9e8a13141c7ebdf765320a37f642c73dfa9da69
Tx public key: d3827874cc7f340172d24e4eabd37f9a3a9f523bafa8f8c39d0106f1594ffe07
Timestamp: 1694720906 Timestamp [UCT]: 2023-09-14 19:48:26 Age [y:d:h:m:s]: 01:193:18:41:40
Block: 848165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399570 RingCT/type: yes/0
Extra: 01d3827874cc7f340172d24e4eabd37f9a3a9f523bafa8f8c39d0106f1594ffe070211000000034b8f5122000000000000000000

1 output(s) for total of 0.949898768000 dcy

stealth address amount amount idx
00: 441278718d329c4ab7ccd33c4a71c48d59427da768ca336694e8c36dae108a7e 0.949898768000 1301751 of 0

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": 848175, "vin": [ { "gen": { "height": 848165 } } ], "vout": [ { "amount": 949898768, "target": { "key": "441278718d329c4ab7ccd33c4a71c48d59427da768ca336694e8c36dae108a7e" } } ], "extra": [ 1, 211, 130, 120, 116, 204, 127, 52, 1, 114, 210, 78, 78, 171, 211, 127, 154, 58, 159, 82, 59, 175, 168, 248, 195, 157, 1, 6, 241, 89, 79, 254, 7, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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