Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf55a92d3348403cd33992c3e627c46f46219af7f62e4cc3f9268de5cae988b2

Tx prefix hash: 2c2da8292deb58b7259f47f3ed874d11f0cd21b3bac84aa0c77a7f845c6bdfae
Tx public key: 8afefd3771a1238efe175ce4825675ed786a8547595e4540d2f9c2a50e4326b0
Timestamp: 1709811211 Timestamp [UCT]: 2024-03-07 11:33:31 Age [y:d:h:m:s]: 01:051:10:31:01
Block: 973096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297771 RingCT/type: yes/0
Extra: 018afefd3771a1238efe175ce4825675ed786a8547595e4540d2f9c2a50e4326b00211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d438dc2dbc4db4cc9d4f1bb25a553ea2aea5caa2af464d5e7534fedd08216af8 0.600000000000 1433027 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": 973106, "vin": [ { "gen": { "height": 973096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d438dc2dbc4db4cc9d4f1bb25a553ea2aea5caa2af464d5e7534fedd08216af8" } } ], "extra": [ 1, 138, 254, 253, 55, 113, 161, 35, 142, 254, 23, 92, 228, 130, 86, 117, 237, 120, 106, 133, 71, 89, 94, 69, 64, 210, 249, 194, 165, 14, 67, 38, 176, 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