Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c254ccc64d3fa81fcf586a6f3ef8ebd5b8b1d957b44d3cea289db01885542a7a

Tx prefix hash: 3ff02d26e892d6db3553e26d0b15c356c3312a8ccf9532712d4cf749df929b9c
Tx public key: 25d0bf3be59726077a3bd19057b41232f1f75cbc4696d8a293c788a7d0514cee
Timestamp: 1707903383 Timestamp [UCT]: 2024-02-14 09:36:23 Age [y:d:h:m:s]: 00:333:16:37:09
Block: 957256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238894 RingCT/type: yes/0
Extra: 0125d0bf3be59726077a3bd19057b41232f1f75cbc4696d8a293c788a7d0514cee0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bd927af074d4f16061cd71bbee2cbd3bc2180271f08851248f5ddc0524bdadc 0.600000000000 1416572 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": 957266, "vin": [ { "gen": { "height": 957256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bd927af074d4f16061cd71bbee2cbd3bc2180271f08851248f5ddc0524bdadc" } } ], "extra": [ 1, 37, 208, 191, 59, 229, 151, 38, 7, 122, 59, 209, 144, 87, 180, 18, 50, 241, 247, 92, 188, 70, 150, 216, 162, 147, 199, 136, 167, 208, 81, 76, 238, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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