Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa910a093d7cf3fc5b29941cc12b0ce456635b953a8c9795c2ef41024ec3a1d4

Tx prefix hash: 994b2c477a3ee4ebba020087acc59d90a6ecb51cb522d7a529085af4e637d6b4
Tx public key: 69b5ac7c9436b2ac621c095c7ee533210f872a8121ac8276f3e03a1f3e821c01
Timestamp: 1696083860 Timestamp [UCT]: 2023-09-30 14:24:20 Age [y:d:h:m:s]: 01:237:20:51:42
Block: 859481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431095 RingCT/type: yes/0
Extra: 0169b5ac7c9436b2ac621c095c7ee533210f872a8121ac8276f3e03a1f3e821c010211000000034b8f5122000000000000000000

1 output(s) for total of 0.871330070000 dcy

stealth address amount amount idx
00: 88521df49ac7c59f2d545da8f1b6183ab147156f4b04890fe25091bd786ffc09 0.871330070000 1313709 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": 859491, "vin": [ { "gen": { "height": 859481 } } ], "vout": [ { "amount": 871330070, "target": { "key": "88521df49ac7c59f2d545da8f1b6183ab147156f4b04890fe25091bd786ffc09" } } ], "extra": [ 1, 105, 181, 172, 124, 148, 54, 178, 172, 98, 28, 9, 92, 126, 229, 51, 33, 15, 135, 42, 129, 33, 172, 130, 118, 243, 224, 58, 31, 62, 130, 28, 1, 2, 17, 0, 0, 0, 3, 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