Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 784e3794dfdd1bd908be0b06b9f51b7223316bfb97583b810c80d036f5b0e615

Tx prefix hash: 03913c256c61cfccfd108dcc6169854ab674145e7e5e7d30cb8157e65266fbe0
Tx public key: c2051104c1854233b800c59c02c6c99dcbf9633716b51e8e0fe7df015ce8271a
Timestamp: 1682799320 Timestamp [UCT]: 2023-04-29 20:15:20 Age [y:d:h:m:s]: 01:345:15:16:16
Block: 749388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508289 RingCT/type: yes/0
Extra: 01c2051104c1854233b800c59c02c6c99dcbf9633716b51e8e0fe7df015ce8271a02110000000375e3f0e9000000000000000000

1 output(s) for total of 2.018211490000 dcy

stealth address amount amount idx
00: 4bf7fe86b3500b327301eb35d75ab2a59a5e136ca33eec01d88bd2a27bd11065 2.018211490000 1197349 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": 749398, "vin": [ { "gen": { "height": 749388 } } ], "vout": [ { "amount": 2018211490, "target": { "key": "4bf7fe86b3500b327301eb35d75ab2a59a5e136ca33eec01d88bd2a27bd11065" } } ], "extra": [ 1, 194, 5, 17, 4, 193, 133, 66, 51, 184, 0, 197, 156, 2, 198, 201, 157, 203, 249, 99, 55, 22, 181, 30, 142, 15, 231, 223, 1, 92, 232, 39, 26, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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