Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13e48ad0bf3463448afa4b4b522556749dc874c4e225b64faef49baea4e7a930

Tx prefix hash: f3657c172a136918ce346de4e6c196ecb69f1a8781863c56424c0913175df1f2
Tx public key: 9e3d3f91a62c914cb7e46bf8867f38140d5993209f00663f5f3e49d1fe85effd
Timestamp: 1735670713 Timestamp [UCT]: 2024-12-31 18:45:13 Age [y:d:h:m:s]: 00:325:01:44:50
Block: 1187339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229855 RingCT/type: yes/0
Extra: 019e3d3f91a62c914cb7e46bf8867f38140d5993209f00663f5f3e49d1fe85effd021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddb5cafdfa0ccfa1741ac28752d58692ac9694e28049e17053469c714ccee962 0.600000000000 1673828 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": 1187349, "vin": [ { "gen": { "height": 1187339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddb5cafdfa0ccfa1741ac28752d58692ac9694e28049e17053469c714ccee962" } } ], "extra": [ 1, 158, 61, 63, 145, 166, 44, 145, 76, 183, 228, 107, 248, 134, 127, 56, 20, 13, 89, 147, 32, 159, 0, 102, 63, 95, 62, 73, 209, 254, 133, 239, 253, 2, 17, 0, 0, 0, 5, 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