Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55aa122a3ef5524746bba61197c093793ddc8b1c803454b37cdf0005d96c5b68

Tx prefix hash: 5b2a04d6217be98429fec0271d6d4c6d6e7f61387d38c6d5c837c2bb6f6a4e9b
Tx public key: 69f7c07d899be234dd1e019dc870f17ca953a783999033a25af4f542ac711092
Timestamp: 1705355287 Timestamp [UCT]: 2024-01-15 21:48:07 Age [y:d:h:m:s]: 01:298:07:24:04
Block: 936122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472018 RingCT/type: yes/0
Extra: 0169f7c07d899be234dd1e019dc870f17ca953a783999033a25af4f542ac7110920211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04407d642408cf44594b9cb1e520fceb92de8a1dbb416e9f8a0c802a9e1cd06f 0.600000000000 1394144 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": 936132, "vin": [ { "gen": { "height": 936122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04407d642408cf44594b9cb1e520fceb92de8a1dbb416e9f8a0c802a9e1cd06f" } } ], "extra": [ 1, 105, 247, 192, 125, 137, 155, 226, 52, 221, 30, 1, 157, 200, 112, 241, 124, 169, 83, 167, 131, 153, 144, 51, 162, 90, 244, 245, 66, 172, 113, 16, 146, 2, 17, 0, 0, 0, 9, 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