Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f15ac9ebada42b8a07026757e5bc632065a22a0bb987ff806d7228f7fc5d6f0

Tx prefix hash: c81a84e6cd9dd841f3fa5fef3ae5ab23e9a92cca64ab0d86ce5d4b62a02dcfb0
Tx public key: 8c2d1d0f3b3a27bb78fa6e33427c0e3aed82cb89470713b2d45c59cc26eece94
Timestamp: 1700412637 Timestamp [UCT]: 2023-11-19 16:50:37 Age [y:d:h:m:s]: 01:140:15:38:15
Block: 895166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361686 RingCT/type: yes/0
Extra: 018c2d1d0f3b3a27bb78fa6e33427c0e3aed82cb89470713b2d45c59cc26eece940211000000024b8f5122000000000000000000

1 output(s) for total of 0.663656621000 dcy

stealth address amount amount idx
00: f48e9935b546b893027ac4fd49dfb0501cfa3d925824a973c2e8deca48cb8f57 0.663656621000 1351389 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": 895176, "vin": [ { "gen": { "height": 895166 } } ], "vout": [ { "amount": 663656621, "target": { "key": "f48e9935b546b893027ac4fd49dfb0501cfa3d925824a973c2e8deca48cb8f57" } } ], "extra": [ 1, 140, 45, 29, 15, 59, 58, 39, 187, 120, 250, 110, 51, 66, 124, 14, 58, 237, 130, 203, 137, 71, 7, 19, 178, 212, 92, 89, 204, 38, 238, 206, 148, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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