Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e38ff05249577c990ea8b991de3d4cc98a62d8a20787edd0655b7c5316636e3

Tx prefix hash: e508602e99eeb7a2be9fcde9b7e94a1530676dd9ff82cbd3d10ebdb1ab61a14f
Tx public key: bf252b3b804a5fcc69b53f08042f8297b1823cacdae59533dc7ccb28c1a68cab
Timestamp: 1705641514 Timestamp [UCT]: 2024-01-19 05:18:34 Age [y:d:h:m:s]: 01:085:15:35:27
Block: 938496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322320 RingCT/type: yes/0
Extra: 01bf252b3b804a5fcc69b53f08042f8297b1823cacdae59533dc7ccb28c1a68cab02110000000379bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6998ca28aced56ae8431800e3bc200f7bb0709625ec67e22e76c95cf43a532d2 0.600000000000 1396566 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": 938506, "vin": [ { "gen": { "height": 938496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6998ca28aced56ae8431800e3bc200f7bb0709625ec67e22e76c95cf43a532d2" } } ], "extra": [ 1, 191, 37, 43, 59, 128, 74, 95, 204, 105, 181, 63, 8, 4, 47, 130, 151, 177, 130, 60, 172, 218, 229, 149, 51, 220, 124, 203, 40, 193, 166, 140, 171, 2, 17, 0, 0, 0, 3, 121, 189, 163, 190, 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