Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcbb65b705d4c63e4739c09e573da46b635c606763caa1a99226698b24dc649a

Tx prefix hash: 6fa3d5ba6ed9be56a2e6a950e7e6c4cfef110f925d338342a38b4774f6e03100
Tx public key: 4fcbff6d9a0e14be6a75d82c0303b534e847e5bd8c0b25f017ee0dc1248b7c68
Timestamp: 1699391740 Timestamp [UCT]: 2023-11-07 21:15:40 Age [y:d:h:m:s]: 01:364:18:27:15
Block: 886702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519595 RingCT/type: yes/0
Extra: 014fcbff6d9a0e14be6a75d82c0303b534e847e5bd8c0b25f017ee0dc1248b7c6802110000000775e3f0e9000000000000000000

1 output(s) for total of 0.707926532000 dcy

stealth address amount amount idx
00: f63e0813a1e37d1c100b2291046796e84b70e06081740093bc65655bb0424510 0.707926532000 1342537 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": 886712, "vin": [ { "gen": { "height": 886702 } } ], "vout": [ { "amount": 707926532, "target": { "key": "f63e0813a1e37d1c100b2291046796e84b70e06081740093bc65655bb0424510" } } ], "extra": [ 1, 79, 203, 255, 109, 154, 14, 20, 190, 106, 117, 216, 44, 3, 3, 181, 52, 232, 71, 229, 189, 140, 11, 37, 240, 23, 238, 13, 193, 36, 139, 124, 104, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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