Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cba712e653be28c4febe28419d9fb70f35ec0cf57a96b17a5beaa29c532380df

Tx prefix hash: ffe23fe21728409cab549a354a0e68151256c0970bf42e8967f2e54cf1312753
Tx public key: 2ebe376d67dfd91e258c9030cf53794d7e65bc23aa7d33fdd03453f34907836b
Timestamp: 1698297254 Timestamp [UCT]: 2023-10-26 05:14:14 Age [y:d:h:m:s]: 01:154:13:46:54
Block: 877848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371466 RingCT/type: yes/0
Extra: 012ebe376d67dfd91e258c9030cf53794d7e65bc23aa7d33fdd03453f34907836b02110000000379bda3be000000000000000000

1 output(s) for total of 0.757399789000 dcy

stealth address amount amount idx
00: ad380d4d06292bbe8be1f2aab8f6d1e9a982e23eee03325de6273e64cbaa87f8 0.757399789000 1333240 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": 877858, "vin": [ { "gen": { "height": 877848 } } ], "vout": [ { "amount": 757399789, "target": { "key": "ad380d4d06292bbe8be1f2aab8f6d1e9a982e23eee03325de6273e64cbaa87f8" } } ], "extra": [ 1, 46, 190, 55, 109, 103, 223, 217, 30, 37, 140, 144, 48, 207, 83, 121, 77, 126, 101, 188, 35, 170, 125, 51, 253, 208, 52, 83, 243, 73, 7, 131, 107, 2, 17, 0, 0, 0, 3, 121, 189, 163, 190, 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