Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9689bf43c36f26ce8ebef8efe1d63130224769c5b7a6c8ad2ad04dffa0a4565

Tx prefix hash: 07ecd940b7bdbe928077df5d001d17499d91a9152bc369e160d22c5367955196
Tx public key: f70d7758b6ef4d0ce4ab5508a593e028557daec8aa1787a504b9b71bb77738f2
Timestamp: 1716853021 Timestamp [UCT]: 2024-05-27 23:37:01 Age [y:d:h:m:s]: 00:184:06:49:32
Block: 1031479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131885 RingCT/type: yes/0
Extra: 01f70d7758b6ef4d0ce4ab5508a593e028557daec8aa1787a504b9b71bb77738f202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbd6b801cfa9df701fa16c7def38c67d8f296e48d7f6a854d976d021a54a8e79 0.600000000000 1499928 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": 1031489, "vin": [ { "gen": { "height": 1031479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbd6b801cfa9df701fa16c7def38c67d8f296e48d7f6a854d976d021a54a8e79" } } ], "extra": [ 1, 247, 13, 119, 88, 182, 239, 77, 12, 228, 171, 85, 8, 165, 147, 224, 40, 85, 125, 174, 200, 170, 23, 135, 165, 4, 185, 183, 27, 183, 119, 56, 242, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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