Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dacd8f1dcee4c3a40ea3c75318a737fd788a360dd3ad98b5f33d9f1bc321165f

Tx prefix hash: d63c28491c243781741ec69759d406d433935f3edf538e85a72eacffbe8cbcf2
Tx public key: 67fb52d5f808afed4bcc249d92f249045098f540487d2428cb5b7167fa5032e1
Timestamp: 1708074514 Timestamp [UCT]: 2024-02-16 09:08:34 Age [y:d:h:m:s]: 01:049:00:09:28
Block: 958677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296070 RingCT/type: yes/0
Extra: 0167fb52d5f808afed4bcc249d92f249045098f540487d2428cb5b7167fa5032e10211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 673aa0ee0922ec773eda6c52444347d3e095ca0edc32c8d3d18586c8bf86a7e0 0.600000000000 1418038 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": 958687, "vin": [ { "gen": { "height": 958677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "673aa0ee0922ec773eda6c52444347d3e095ca0edc32c8d3d18586c8bf86a7e0" } } ], "extra": [ 1, 103, 251, 82, 213, 248, 8, 175, 237, 75, 204, 36, 157, 146, 242, 73, 4, 80, 152, 245, 64, 72, 125, 36, 40, 203, 91, 113, 103, 250, 80, 50, 225, 2, 17, 0, 0, 0, 2, 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