Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d93f57af3fc45358a0c8bc4e84ef7736e1a569c1d3dc206d9943496e84036a4

Tx prefix hash: d4e1699a8662d28bfb8db5a25f60169b168c45f7003c6bae5c952e328d6f42d4
Tx public key: 4fc8dd9894b51eb42b73d1c4b31e323618b56c0f9f1a9a8748482255dbe57259
Timestamp: 1712907596 Timestamp [UCT]: 2024-04-12 07:39:56 Age [y:d:h:m:s]: 01:217:18:48:14
Block: 998739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414340 RingCT/type: yes/0
Extra: 014fc8dd9894b51eb42b73d1c4b31e323618b56c0f9f1a9a8748482255dbe5725902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0d02f54ff965dc73d06fd13ea54a1f6e3d3c2ee13d6bbc7b9fc95126d1dc8a1 0.600000000000 1459191 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": 998749, "vin": [ { "gen": { "height": 998739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0d02f54ff965dc73d06fd13ea54a1f6e3d3c2ee13d6bbc7b9fc95126d1dc8a1" } } ], "extra": [ 1, 79, 200, 221, 152, 148, 181, 30, 180, 43, 115, 209, 196, 179, 30, 50, 54, 24, 181, 108, 15, 159, 26, 154, 135, 72, 72, 34, 85, 219, 229, 114, 89, 2, 17, 0, 0, 0, 4, 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