Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56421c5f30f5a537da73ab0397606f15e438b6ade8cac5895a629089606436a6

Tx prefix hash: 1715f27ff0ca35841f13037e90aeff2bb096a6b4165f87c13f14513dd77a7a6a
Tx public key: 843e3a11ae79b0534c57612284dc39dd7f7549763f34c43070ee6ede80f38f3b
Timestamp: 1695555695 Timestamp [UCT]: 2023-09-24 11:41:35 Age [y:d:h:m:s]: 01:180:18:53:26
Block: 855097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390271 RingCT/type: yes/0
Extra: 01843e3a11ae79b0534c57612284dc39dd7f7549763f34c43070ee6ede80f38f3b021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.900966660000 dcy

stealth address amount amount idx
00: e5b3f3f0e36e95f7f0acf3611b78c2c94affd3ce979f4617ba63b04ca7e88403 0.900966660000 1309101 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": 855107, "vin": [ { "gen": { "height": 855097 } } ], "vout": [ { "amount": 900966660, "target": { "key": "e5b3f3f0e36e95f7f0acf3611b78c2c94affd3ce979f4617ba63b04ca7e88403" } } ], "extra": [ 1, 132, 62, 58, 17, 174, 121, 176, 83, 76, 87, 97, 34, 132, 220, 57, 221, 127, 117, 73, 118, 63, 52, 196, 48, 112, 238, 110, 222, 128, 243, 143, 59, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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