Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 439e45d7023ff9fe5cb7a0a37bb521fc500246f8c3c60419b284e19ab3431c32

Tx prefix hash: 0814a60d9cef183668fc1cefdf4c92c76e1fc15a8fbc88823427bdea660305f3
Tx public key: d3bbe6b3e695aa035ce730f4bbf2f0dcc13f0876a2e2ba5818e7ad183c1ca62f
Timestamp: 1701486413 Timestamp [UCT]: 2023-12-02 03:06:53 Age [y:d:h:m:s]: 01:163:17:50:44
Block: 904058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378221 RingCT/type: yes/0
Extra: 01d3bbe6b3e695aa035ce730f4bbf2f0dcc13f0876a2e2ba5818e7ad183c1ca62f02110000000446113aa8000000000000000000

1 output(s) for total of 0.620126843000 dcy

stealth address amount amount idx
00: e641829856314a979ab3716e12e7aa0f8189414c9d7de6e85d78fbc7e4508cd8 0.620126843000 1360761 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": 904068, "vin": [ { "gen": { "height": 904058 } } ], "vout": [ { "amount": 620126843, "target": { "key": "e641829856314a979ab3716e12e7aa0f8189414c9d7de6e85d78fbc7e4508cd8" } } ], "extra": [ 1, 211, 187, 230, 179, 230, 149, 170, 3, 92, 231, 48, 244, 187, 242, 240, 220, 193, 63, 8, 118, 162, 226, 186, 88, 24, 231, 173, 24, 60, 28, 166, 47, 2, 17, 0, 0, 0, 4, 70, 17, 58, 168, 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