Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43ca45f6623c007fb4fe263436abf96d7af4b1c7ff5e61ac66de2f8769d000a7

Tx prefix hash: cac49aec8401c8e4ea58fcf86ece645cdd3836fdecce43f247c79d5d13c56819
Tx public key: a670f3415f38819500d1f9e91e3fdfd36ce922f1e661d25c77ecd155023c70c2
Timestamp: 1610116706 Timestamp [UCT]: 2021-01-08 14:38:26 Age [y:d:h:m:s]: 04:066:00:58:51
Block: 176157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1063061 RingCT/type: yes/0
Extra: 01a670f3415f38819500d1f9e91e3fdfd36ce922f1e661d25c77ecd155023c70c2021100000052c6b81c9d000000000000000000

1 output(s) for total of 160.073481071000 dcy

stealth address amount amount idx
00: 28d57e9417b1d690c09b88a4cf1440a24bf0415281d94bf964143f29883d5f24 160.073481071000 337229 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": 176167, "vin": [ { "gen": { "height": 176157 } } ], "vout": [ { "amount": 160073481071, "target": { "key": "28d57e9417b1d690c09b88a4cf1440a24bf0415281d94bf964143f29883d5f24" } } ], "extra": [ 1, 166, 112, 243, 65, 95, 56, 129, 149, 0, 209, 249, 233, 30, 63, 223, 211, 108, 233, 34, 241, 230, 97, 210, 92, 119, 236, 209, 85, 2, 60, 112, 194, 2, 17, 0, 0, 0, 82, 198, 184, 28, 157, 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