Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cbb6080971118f8754581a6f4ee23601acd24defcf5a47fc89cdfdb9bbc541b

Tx prefix hash: 7dbe427bbf2727adb28c7475e5f9625310f34be1cb84361360c72fefafc4c319
Tx public key: d5a48b1ec3186a5faf4579d6ccb76bf09c395ec06369f3047a8298e2d98976d2
Timestamp: 1706945617 Timestamp [UCT]: 2024-02-03 07:33:37 Age [y:d:h:m:s]: 01:332:00:51:32
Block: 949313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496160 RingCT/type: yes/0
Extra: 01d5a48b1ec3186a5faf4579d6ccb76bf09c395ec06369f3047a8298e2d98976d20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84b1f3f9a92923d8c239f777b665ee7638263a0bd90f5277a8f4e58ed6e0d8f2 0.600000000000 1407837 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": 949323, "vin": [ { "gen": { "height": 949313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84b1f3f9a92923d8c239f777b665ee7638263a0bd90f5277a8f4e58ed6e0d8f2" } } ], "extra": [ 1, 213, 164, 139, 30, 195, 24, 106, 95, 175, 69, 121, 214, 204, 183, 107, 240, 156, 57, 94, 192, 99, 105, 243, 4, 122, 130, 152, 226, 217, 137, 118, 210, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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