Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4605e745a64384a72b18096196410ac6d8b85456970401338cfee8ce32244b6

Tx prefix hash: 0993fd5f78f657fe20731adddc56513e073e236b04a5e7a4e6f8bcbcc0235a3d
Tx public key: 4bbde54edbea6f3a93f799d98fc21fe5f4394a2e58aba819ad87a1ca4b57c474
Timestamp: 1719372255 Timestamp [UCT]: 2024-06-26 03:24:15 Age [y:d:h:m:s]: 00:282:03:52:37
Block: 1052340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201631 RingCT/type: yes/0
Extra: 014bbde54edbea6f3a93f799d98fc21fe5f4394a2e58aba819ad87a1ca4b57c4740211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b821537c26d29789d305f2a92be1181e07a6b75c9401b78a5d732cd8a1373d91 0.600000000000 1522663 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": 1052350, "vin": [ { "gen": { "height": 1052340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b821537c26d29789d305f2a92be1181e07a6b75c9401b78a5d732cd8a1373d91" } } ], "extra": [ 1, 75, 189, 229, 78, 219, 234, 111, 58, 147, 247, 153, 217, 143, 194, 31, 229, 244, 57, 74, 46, 88, 171, 168, 25, 173, 135, 161, 202, 75, 87, 196, 116, 2, 17, 0, 0, 0, 5, 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