Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7048a032cefc019cf59893bb794f114e66bb6c9cc5ae643aa07e8632c3c17dd8

Tx prefix hash: 4fe236946e2fcc3d9f05fa5594a8f1809d07af58ba19f9ffc2734bb375cf352d
Tx public key: 7b8c527c4befd0e8efa8cfcbf01dad178680e8193323f86db328d74d12b69bf8
Timestamp: 1724071401 Timestamp [UCT]: 2024-08-19 12:43:21 Age [y:d:h:m:s]: 01:079:07:55:57
Block: 1091312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315141 RingCT/type: yes/0
Extra: 017b8c527c4befd0e8efa8cfcbf01dad178680e8193323f86db328d74d12b69bf802110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ff6e71a88a32dc099900e8ce2e8c507c1a0509bb94c0c10b0ba598fb2f76610 0.600000000000 1565943 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": 1091322, "vin": [ { "gen": { "height": 1091312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ff6e71a88a32dc099900e8ce2e8c507c1a0509bb94c0c10b0ba598fb2f76610" } } ], "extra": [ 1, 123, 140, 82, 124, 75, 239, 208, 232, 239, 168, 207, 203, 240, 29, 173, 23, 134, 128, 232, 25, 51, 35, 248, 109, 179, 40, 215, 77, 18, 182, 155, 248, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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