Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fe3f4d4458e780ac53f8c0d9f5081dc45dfac59fd7a3b6016a46d86a594ac2f

Tx prefix hash: 34c7c61f8d397f0dfd4a8ce49f3b9ea63839090cf51635c50869c14ddbefa7a3
Tx public key: 4b9818413ba49f3f27db70b079cc9edf1b9c840d6610601226a75ed2f77163b3
Timestamp: 1699148341 Timestamp [UCT]: 2023-11-05 01:39:01 Age [y:d:h:m:s]: 01:150:23:08:05
Block: 884937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368841 RingCT/type: yes/0
Extra: 014b9818413ba49f3f27db70b079cc9edf1b9c840d6610601226a75ed2f77163b3021100000003faf35c9c000000000000000000

1 output(s) for total of 0.717523897000 dcy

stealth address amount amount idx
00: 5c1fb7344ab0adfd959e7a77617b58435e022e9c19377d1b25b6f4a09c3758b8 0.717523897000 1340686 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": 884947, "vin": [ { "gen": { "height": 884937 } } ], "vout": [ { "amount": 717523897, "target": { "key": "5c1fb7344ab0adfd959e7a77617b58435e022e9c19377d1b25b6f4a09c3758b8" } } ], "extra": [ 1, 75, 152, 24, 65, 59, 164, 159, 63, 39, 219, 112, 176, 121, 204, 158, 223, 27, 156, 132, 13, 102, 16, 96, 18, 38, 167, 94, 210, 247, 113, 99, 179, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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