Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4389a4532f3211f231237ebacba280136c4caeac4ba4fb17a920dae63f691b

Tx prefix hash: 0eb41370826289639ab15188e66e2922b93bc7c70a6cbd1d03458cf73add5829
Tx public key: 87704358ca5e99d70fe0f11bd8175d3420b4f6b2c3f88165ee0f7a6484a695bc
Timestamp: 1696262154 Timestamp [UCT]: 2023-10-02 15:55:54 Age [y:d:h:m:s]: 01:253:04:37:05
Block: 860960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442038 RingCT/type: yes/0
Extra: 0187704358ca5e99d70fe0f11bd8175d3420b4f6b2c3f88165ee0f7a6484a695bc02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.861553318000 dcy

stealth address amount amount idx
00: 599128873cf9c9d4068e0637da512acdc3ff5f7a517577617a67a3c628b4bdcd 0.861553318000 1315270 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": 860970, "vin": [ { "gen": { "height": 860960 } } ], "vout": [ { "amount": 861553318, "target": { "key": "599128873cf9c9d4068e0637da512acdc3ff5f7a517577617a67a3c628b4bdcd" } } ], "extra": [ 1, 135, 112, 67, 88, 202, 94, 153, 215, 15, 224, 241, 27, 216, 23, 93, 52, 32, 180, 246, 178, 195, 248, 129, 101, 238, 15, 122, 100, 132, 166, 149, 188, 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