Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8b292e204131d250d7cba04813e4fe59d13c7b098a5838b2f2041479dd9eb9f

Tx prefix hash: c48700df8f42571dca024bc2aabc912e0c5f2dc79e405fb49ceb77e435789a79
Tx public key: 595d449500b3fb10321750a89e47762b5fd8d0d85516e4dd4fd58425c545cd22
Timestamp: 1711975481 Timestamp [UCT]: 2024-04-01 12:44:41 Age [y:d:h:m:s]: 01:008:05:04:07
Block: 990996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266862 RingCT/type: yes/0
Extra: 01595d449500b3fb10321750a89e47762b5fd8d0d85516e4dd4fd58425c545cd220211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29bff81cc7856762f84fe21fa4e5da7a55f89b313a1525ad7b65ab5353ac51e8 0.600000000000 1451328 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": 991006, "vin": [ { "gen": { "height": 990996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29bff81cc7856762f84fe21fa4e5da7a55f89b313a1525ad7b65ab5353ac51e8" } } ], "extra": [ 1, 89, 93, 68, 149, 0, 179, 251, 16, 50, 23, 80, 168, 158, 71, 118, 43, 95, 216, 208, 216, 85, 22, 228, 221, 79, 213, 132, 37, 197, 69, 205, 34, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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