Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0573072caf1b4308a3ed1d4faf65aa5f73b30aab5b6018adfeda983d09c06f

Tx prefix hash: 961168f16ae7b6aac99313411c936a9f473e379e81d55ac850955e7e99652399
Tx public key: 569770b5ae14870424d9377a8e59624bc703292ead3e84ff4b42bc6bc0f719a7
Timestamp: 1731341886 Timestamp [UCT]: 2024-11-11 16:18:06 Age [y:d:h:m:s]: 00:146:06:46:12
Block: 1151486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104370 RingCT/type: yes/0
Extra: 01569770b5ae14870424d9377a8e59624bc703292ead3e84ff4b42bc6bc0f719a70211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0a1b6332c4caa2000030fd267c24caccf2841cd168b9af96073ab56d14e399f 0.600000000000 1637025 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": 1151496, "vin": [ { "gen": { "height": 1151486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0a1b6332c4caa2000030fd267c24caccf2841cd168b9af96073ab56d14e399f" } } ], "extra": [ 1, 86, 151, 112, 181, 174, 20, 135, 4, 36, 217, 55, 122, 142, 89, 98, 75, 199, 3, 41, 46, 173, 62, 132, 255, 75, 66, 188, 107, 192, 247, 25, 167, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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