Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42e4351c44c31861c58f999f866ad71325a915159c546520c3201ccc13c494c3

Tx prefix hash: a6fd8a42cfaf00858925d6b33d5c9807e2d21832634e22fd64feff7abccad33c
Tx public key: 7e7444dab1167dd645d9d17d7fb255da1b471e610f3b526abaad19f7beb50333
Timestamp: 1698281556 Timestamp [UCT]: 2023-10-26 00:52:36 Age [y:d:h:m:s]: 01:149:08:05:52
Block: 877723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367722 RingCT/type: yes/0
Extra: 017e7444dab1167dd645d9d17d7fb255da1b471e610f3b526abaad19f7beb50333021100000001faf35c9c000000000000000000

1 output(s) for total of 0.758122449000 dcy

stealth address amount amount idx
00: da3d294806c526a353e6c1f8339d202953a1b0efe648d2d6a05947bcdc68fb07 0.758122449000 1333109 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": 877733, "vin": [ { "gen": { "height": 877723 } } ], "vout": [ { "amount": 758122449, "target": { "key": "da3d294806c526a353e6c1f8339d202953a1b0efe648d2d6a05947bcdc68fb07" } } ], "extra": [ 1, 126, 116, 68, 218, 177, 22, 125, 214, 69, 217, 209, 125, 127, 178, 85, 218, 27, 71, 30, 97, 15, 59, 82, 106, 186, 173, 25, 247, 190, 181, 3, 51, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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