Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dbb4ef3f3655d95529e6a449da14efb5d04d441392482918c4803a63bd2e7e3

Tx prefix hash: f553d0f247806dddbb48cecafb5507903a43a3f6f5df77f3c0e353d70eca9676
Tx public key: e7bd7767f8edb5641660d8277ff3a5462abd707f50ff34ee32d3a8652970e16c
Timestamp: 1708332917 Timestamp [UCT]: 2024-02-19 08:55:17 Age [y:d:h:m:s]: 01:065:07:33:50
Block: 960827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307726 RingCT/type: yes/0
Extra: 01e7bd7767f8edb5641660d8277ff3a5462abd707f50ff34ee32d3a8652970e16c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23b6008256c7dd9139d97ee5c15c69f9f6f481da7a3e8def21a5e9dc393c961f 0.600000000000 1420414 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": 960837, "vin": [ { "gen": { "height": 960827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23b6008256c7dd9139d97ee5c15c69f9f6f481da7a3e8def21a5e9dc393c961f" } } ], "extra": [ 1, 231, 189, 119, 103, 248, 237, 181, 100, 22, 96, 216, 39, 127, 243, 165, 70, 42, 189, 112, 127, 80, 255, 52, 238, 50, 211, 168, 101, 41, 112, 225, 108, 2, 17, 0, 0, 0, 1, 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