Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2c56088fd66562606eabcab075fb7f35ac86a6a5acbe172ba343f95b438d074

Tx prefix hash: 46e11e0c63f8244d89f5bddf0704c903c411f48b9d83df0d20e56839a7dc46ec
Tx public key: 00e820f0d0d5e56ea098ce2f1f558d1b38d0643df8847d9cd10dad00dee013a0
Timestamp: 1674435748 Timestamp [UCT]: 2023-01-23 01:02:28 Age [y:d:h:m:s]: 02:286:13:35:47
Block: 680677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724177 RingCT/type: yes/0
Extra: 0100e820f0d0d5e56ea098ce2f1f558d1b38d0643df8847d9cd10dad00dee013a00211000000025029cbac000000000000000000

1 output(s) for total of 3.409058691000 dcy

stealth address amount amount idx
00: f8609a8981f2a208dc558c7e12b249a872aa0139eb4b3161f354bb6b1750a8f5 3.409058691000 1122736 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": 680687, "vin": [ { "gen": { "height": 680677 } } ], "vout": [ { "amount": 3409058691, "target": { "key": "f8609a8981f2a208dc558c7e12b249a872aa0139eb4b3161f354bb6b1750a8f5" } } ], "extra": [ 1, 0, 232, 32, 240, 208, 213, 229, 110, 160, 152, 206, 47, 31, 85, 141, 27, 56, 208, 100, 61, 248, 132, 125, 156, 209, 13, 173, 0, 222, 224, 19, 160, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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