Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d00c1de776402ede2adbb5874580f1cc970a17389439782aa14536934e6c50d6

Tx prefix hash: 7e6ad65ed538c2b9f82a05ec8117a85c03ef860f500d7eec19100eaa906ac1cf
Tx public key: 4c12f6ac16b90bc3b4ea31b07732c1639b455f74e452a5e99e3f248b3ab6b16d
Timestamp: 1702105670 Timestamp [UCT]: 2023-12-09 07:07:50 Age [y:d:h:m:s]: 01:082:12:49:38
Block: 909197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320110 RingCT/type: yes/0
Extra: 014c12f6ac16b90bc3b4ea31b07732c1639b455f74e452a5e99e3f248b3ab6b16d02110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70dd1c41c25f3bc3d2d03256e78f452c4835e140a4fda539635b852d609d31d9 0.600000000000 1366266 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": 909207, "vin": [ { "gen": { "height": 909197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70dd1c41c25f3bc3d2d03256e78f452c4835e140a4fda539635b852d609d31d9" } } ], "extra": [ 1, 76, 18, 246, 172, 22, 185, 11, 195, 180, 234, 49, 176, 119, 50, 193, 99, 155, 69, 95, 116, 228, 82, 165, 233, 158, 63, 36, 139, 58, 182, 177, 109, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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