Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c6f4193f71c78d3c91a6fcd774723186d5e8886d019e92463339fc2365891d8

Tx prefix hash: b430771fbacbdd1e1dc65ff1af4e942a20c8961f7e7719285fa0751c2c3d44cb
Tx public key: 49fc66926b10df9e5ec23d3602e8fd2eba6bbaf0c7468efa4793c61f9ba1fb12
Timestamp: 1698005564 Timestamp [UCT]: 2023-10-22 20:12:44 Age [y:d:h:m:s]: 01:164:11:00:29
Block: 875417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378553 RingCT/type: yes/0
Extra: 0149fc66926b10df9e5ec23d3602e8fd2eba6bbaf0c7468efa4793c61f9ba1fb1202110000000175e3f0e9000000000000000000

1 output(s) for total of 0.771578461000 dcy

stealth address amount amount idx
00: f907b40136d9c1e5c15daaaf515b49e5345e01d003bc7b277d2e13e7c55a11bc 0.771578461000 1330671 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": 875427, "vin": [ { "gen": { "height": 875417 } } ], "vout": [ { "amount": 771578461, "target": { "key": "f907b40136d9c1e5c15daaaf515b49e5345e01d003bc7b277d2e13e7c55a11bc" } } ], "extra": [ 1, 73, 252, 102, 146, 107, 16, 223, 158, 94, 194, 61, 54, 2, 232, 253, 46, 186, 107, 186, 240, 199, 70, 142, 250, 71, 147, 198, 31, 155, 161, 251, 18, 2, 17, 0, 0, 0, 1, 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