Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53d33019ab15dafeccc423042bce343eeea0763f4040d166b00dd7244f406bdb

Tx prefix hash: 244bfd5e5169124ddfe1b6f2d9c96b296f081a929a6173487fa0a33e9e8131d9
Tx public key: 1b36c3e28a8340eaed6c57f1d594f487d24ba5de80dda9405f4610b88fd5f758
Timestamp: 1708129984 Timestamp [UCT]: 2024-02-17 00:33:04 Age [y:d:h:m:s]: 01:038:14:28:33
Block: 959142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288599 RingCT/type: yes/0
Extra: 011b36c3e28a8340eaed6c57f1d594f487d24ba5de80dda9405f4610b88fd5f7580211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a9a35e5997d034b9acb8bb639eb81789bef69df50166e52b40bb20650b6e7cf 0.600000000000 1418673 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": 959152, "vin": [ { "gen": { "height": 959142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a9a35e5997d034b9acb8bb639eb81789bef69df50166e52b40bb20650b6e7cf" } } ], "extra": [ 1, 27, 54, 195, 226, 138, 131, 64, 234, 237, 108, 87, 241, 213, 148, 244, 135, 210, 75, 165, 222, 128, 221, 169, 64, 95, 70, 16, 184, 143, 213, 247, 88, 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