Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b699346929a4fe86ac407b87eb81c2b5ea9656ac033498244e17d9bee5026eff

Tx prefix hash: d2b3432f778cd1f9c26e31562ae534fb543061fd9bb0e84dd8850d3fcc7c2505
Tx public key: d5cd5cb32ce22ac31bc793d230ad5d43cb32ff10bb94e5f60bf465636447b222
Timestamp: 1711992792 Timestamp [UCT]: 2024-04-01 17:33:12 Age [y:d:h:m:s]: 01:074:19:08:12
Block: 991144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314392 RingCT/type: yes/0
Extra: 01d5cd5cb32ce22ac31bc793d230ad5d43cb32ff10bb94e5f60bf465636447b2220211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0a8c2ea23c7839417aaf46407b2dcf3d78c589d057e8e385d85c53b8e32e6d9 0.600000000000 1451478 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": 991154, "vin": [ { "gen": { "height": 991144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0a8c2ea23c7839417aaf46407b2dcf3d78c589d057e8e385d85c53b8e32e6d9" } } ], "extra": [ 1, 213, 205, 92, 179, 44, 226, 42, 195, 27, 199, 147, 210, 48, 173, 93, 67, 203, 50, 255, 16, 187, 148, 229, 246, 11, 244, 101, 99, 100, 71, 178, 34, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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