Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c37d21276e8c9a033ac1a18bdd88c29842a8190b9e515f26b9b1de61bf4674

Tx prefix hash: d77401a3b324907855a6d32cc0a7e2d573a8f761af35c9029f4ad7d289bf4aac
Tx public key: 8ed39e19df718472fb0bad76ff9eee722756f72184674c7d867ed5266a639b92
Timestamp: 1713703135 Timestamp [UCT]: 2024-04-21 12:38:55 Age [y:d:h:m:s]: 00:309:23:39:02
Block: 1005353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221569 RingCT/type: yes/0
Extra: 018ed39e19df718472fb0bad76ff9eee722756f72184674c7d867ed5266a639b920211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 735e8b264e00fdf383f4c7aae96db64c2790e91f9472324864f1ba1a00a6a783 0.600000000000 1465979 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": 1005363, "vin": [ { "gen": { "height": 1005353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "735e8b264e00fdf383f4c7aae96db64c2790e91f9472324864f1ba1a00a6a783" } } ], "extra": [ 1, 142, 211, 158, 25, 223, 113, 132, 114, 251, 11, 173, 118, 255, 158, 238, 114, 39, 86, 247, 33, 132, 103, 76, 125, 134, 126, 213, 38, 106, 99, 155, 146, 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