Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fc539447c82fe69b22d633aab0a9898681c4aded5ed522d35eaf0c569da71ca

Tx prefix hash: 52f40cda048b578e23a71b87012c8ff1bc195ff0a9a684442fce8fbfb84af0c0
Tx public key: 813057f5b30199f1264d5a7075c80ac13f61aa76b831f0f83ea6ae752a43734e
Timestamp: 1715231209 Timestamp [UCT]: 2024-05-09 05:06:49 Age [y:d:h:m:s]: 00:248:08:32:30
Block: 1018020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177754 RingCT/type: yes/0
Extra: 01813057f5b30199f1264d5a7075c80ac13f61aa76b831f0f83ea6ae752a43734e0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 558409d6f2db5e0c9511656557ee4506e3f6cc12fdd95358e4cf6410573d1be4 0.600000000000 1481805 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": 1018030, "vin": [ { "gen": { "height": 1018020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "558409d6f2db5e0c9511656557ee4506e3f6cc12fdd95358e4cf6410573d1be4" } } ], "extra": [ 1, 129, 48, 87, 245, 179, 1, 153, 241, 38, 77, 90, 112, 117, 200, 10, 193, 63, 97, 170, 118, 184, 49, 240, 248, 62, 166, 174, 117, 42, 67, 115, 78, 2, 17, 0, 0, 0, 6, 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