Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f6d7fdba51139649d4ff6a7a89622d8dc711f01fc9c852aa05503eedc2c5245

Tx prefix hash: 930491c7801aaca0843215b1c18bee027c80e5fb7312652954022d052f443e38
Tx public key: bf25f0c3d86b6ff4f80339e5069fe7f763dc491c0505f84e7f38317db0ee09e6
Timestamp: 1710434593 Timestamp [UCT]: 2024-03-14 16:43:13 Age [y:d:h:m:s]: 00:345:14:17:14
Block: 978281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247042 RingCT/type: yes/0
Extra: 01bf25f0c3d86b6ff4f80339e5069fe7f763dc491c0505f84e7f38317db0ee09e602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2bcedf83931ac14c4599416dd6ed6bbd204613a98d396da7f53f88049ca5538 0.600000000000 1438304 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": 978291, "vin": [ { "gen": { "height": 978281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2bcedf83931ac14c4599416dd6ed6bbd204613a98d396da7f53f88049ca5538" } } ], "extra": [ 1, 191, 37, 240, 195, 216, 107, 111, 244, 248, 3, 57, 229, 6, 159, 231, 247, 99, 220, 73, 28, 5, 5, 248, 78, 127, 56, 49, 125, 176, 238, 9, 230, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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