Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7325ad44bcd1fca5f130ec0c99c063308ceaab8b6e2481180f193f884d3b9d2

Tx prefix hash: dd5d0a0d86d4631dee28b643c5004d59e7f22a7c72038ba4e02395ed05a1f879
Tx public key: 32763520d8c094a2c2fa0dfcbc7d6266ec05ca9591446fa9eae09aa959c5f0b5
Timestamp: 1708154705 Timestamp [UCT]: 2024-02-17 07:25:05 Age [y:d:h:m:s]: 01:038:05:49:38
Block: 959346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288356 RingCT/type: yes/0
Extra: 0132763520d8c094a2c2fa0dfcbc7d6266ec05ca9591446fa9eae09aa959c5f0b50211000000023f0590f7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd3d3e428c6cdccd7bddabb16de710da8f6f4687ca5affcfd5b79310c0eeb77d 0.600000000000 1418881 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": 959356, "vin": [ { "gen": { "height": 959346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd3d3e428c6cdccd7bddabb16de710da8f6f4687ca5affcfd5b79310c0eeb77d" } } ], "extra": [ 1, 50, 118, 53, 32, 216, 192, 148, 162, 194, 250, 13, 252, 188, 125, 98, 102, 236, 5, 202, 149, 145, 68, 111, 169, 234, 224, 154, 169, 89, 197, 240, 181, 2, 17, 0, 0, 0, 2, 63, 5, 144, 247, 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