Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff68a3a0bc1c63d8d52b7dbc8fcdb2078d7ebabb793c8aecb50f4889c501f3d2

Tx prefix hash: d77041b1a60bcb8ff1f2c1e6b6ac3d2f2a343074a5996c7d81150717aa4996fd
Tx public key: 9a6ea786acca443a6e6e4c7f64f7edd7dd017522adcc37ba4b4b856cc1e5f01e
Timestamp: 1735466379 Timestamp [UCT]: 2024-12-29 09:59:39 Age [y:d:h:m:s]: 00:108:08:44:36
Block: 1185643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77249 RingCT/type: yes/0
Extra: 019a6ea786acca443a6e6e4c7f64f7edd7dd017522adcc37ba4b4b856cc1e5f01e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e02667126947e5761e4bafeef87b43a89abcb48639034a55b05918ef4632f75e 0.600000000000 1672118 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": 1185653, "vin": [ { "gen": { "height": 1185643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e02667126947e5761e4bafeef87b43a89abcb48639034a55b05918ef4632f75e" } } ], "extra": [ 1, 154, 110, 167, 134, 172, 202, 68, 58, 110, 110, 76, 127, 100, 247, 237, 215, 221, 1, 117, 34, 173, 204, 55, 186, 75, 75, 133, 108, 193, 229, 240, 30, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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