Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01c8a144f3115823ad3b736ebc8ee1aed65cc3f6b85003e346114ea94ee1ed7d

Tx prefix hash: f8754fecec6f74f471ed69a67815356ac872787cd525e0c89271cfb23e396eb3
Tx public key: 7d2e0c42ac21ce03f8d153220c1fb2301505774b8ce5bc1f7fd9f8ddbec9784a
Timestamp: 1699063105 Timestamp [UCT]: 2023-11-04 01:58:25 Age [y:d:h:m:s]: 01:132:01:59:15
Block: 884186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355390 RingCT/type: yes/0
Extra: 017d2e0c42ac21ce03f8d153220c1fb2301505774b8ce5bc1f7fd9f8ddbec9784a02110000000233af99f4000000000000000000

1 output(s) for total of 0.721646892000 dcy

stealth address amount amount idx
00: 8f74d982e6cef19f26a38e9082bebe80e9e39df0ed255449cff7984a0527993d 0.721646892000 1339921 of 0

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": 884196, "vin": [ { "gen": { "height": 884186 } } ], "vout": [ { "amount": 721646892, "target": { "key": "8f74d982e6cef19f26a38e9082bebe80e9e39df0ed255449cff7984a0527993d" } } ], "extra": [ 1, 125, 46, 12, 66, 172, 33, 206, 3, 248, 209, 83, 34, 12, 31, 178, 48, 21, 5, 119, 75, 140, 229, 188, 31, 127, 217, 248, 221, 190, 201, 120, 74, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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