Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4d6d800fe5ef7bce08e8f6b5724ae8c77af7c6d38e66e921908de5ce999c259

Tx prefix hash: 1d46402ccaf83a1166847a17688a05da4efb2b8e1a53316121fb730d63d79237
Tx public key: 59b43833217d5836667dba89c1f9a5f871a70bb942b03f19d90f6a78aa3342f4
Timestamp: 1737021948 Timestamp [UCT]: 2025-01-16 10:05:48 Age [y:d:h:m:s]: 00:060:02:25:06
Block: 1198520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42749 RingCT/type: yes/0
Extra: 0159b43833217d5836667dba89c1f9a5f871a70bb942b03f19d90f6a78aa3342f4021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4522ccc16fcdd05cc2c89c64f9c2c680446e483d64cda3c69eb91e97b58d7fb6 0.600000000000 1685145 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": 1198530, "vin": [ { "gen": { "height": 1198520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4522ccc16fcdd05cc2c89c64f9c2c680446e483d64cda3c69eb91e97b58d7fb6" } } ], "extra": [ 1, 89, 180, 56, 51, 33, 125, 88, 54, 102, 125, 186, 137, 193, 249, 165, 248, 113, 167, 11, 185, 66, 176, 63, 25, 217, 15, 106, 120, 170, 51, 66, 244, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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