Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa829c1f5c8253fda496573b656735ba7e8bde7684b5e1effb095b0cacd8ad41

Tx prefix hash: 8832be9781670b578e5c69215cfcf716c808bbf9c6e093c433f5ae9205f81b8e
Tx public key: 526666b1dbff43b75ddb828db87b606d428edde68eaf7d6afe83c0ebc11f09dc
Timestamp: 1676387914 Timestamp [UCT]: 2023-02-14 15:18:34 Age [y:d:h:m:s]: 01:278:16:53:33
Block: 696885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460103 RingCT/type: yes/0
Extra: 01526666b1dbff43b75ddb828db87b606d428edde68eaf7d6afe83c0ebc11f09dc021100000003835e4d22000000000000000000

1 output(s) for total of 3.012524740000 dcy

stealth address amount amount idx
00: af7d24ed24f14d8ca41fb1c33e67a2221b3afd691fb2d154200cec2b5d6ca0e4 3.012524740000 1139942 of 0

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": 696895, "vin": [ { "gen": { "height": 696885 } } ], "vout": [ { "amount": 3012524740, "target": { "key": "af7d24ed24f14d8ca41fb1c33e67a2221b3afd691fb2d154200cec2b5d6ca0e4" } } ], "extra": [ 1, 82, 102, 102, 177, 219, 255, 67, 183, 93, 219, 130, 141, 184, 123, 96, 109, 66, 142, 221, 230, 142, 175, 125, 106, 254, 131, 192, 235, 193, 31, 9, 220, 2, 17, 0, 0, 0, 3, 131, 94, 77, 34, 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