Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10e47342f002657482c389b3415238d2afc40473c5a4dbd5e231ac1bfc5867fc

Tx prefix hash: 67a012c7f3dbd1c3dcde111aad3e123ba2ae836fae13bfba6bc98cfffbae9202
Tx public key: 3014153dcf3718e9cdae7b3b0aea19a6f65342620d77b6c55c9a3d32f78fcb75
Timestamp: 1583082470 Timestamp [UCT]: 2020-03-01 17:07:50 Age [y:d:h:m:s]: 04:270:06:25:49
Block: 74701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087030 RingCT/type: yes/0
Extra: 013014153dcf3718e9cdae7b3b0aea19a6f65342620d77b6c55c9a3d32f78fcb750211000000ae0aca7173000000000000000000

1 output(s) for total of 347.124586044000 dcy

stealth address amount amount idx
00: e434221b6bd90ca9ea21a6f9fca25f382678cbff77eba215b31a3739108c2a7d 347.124586044000 138181 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": 74711, "vin": [ { "gen": { "height": 74701 } } ], "vout": [ { "amount": 347124586044, "target": { "key": "e434221b6bd90ca9ea21a6f9fca25f382678cbff77eba215b31a3739108c2a7d" } } ], "extra": [ 1, 48, 20, 21, 61, 207, 55, 24, 233, 205, 174, 123, 59, 10, 234, 25, 166, 246, 83, 66, 98, 13, 119, 182, 197, 92, 154, 61, 50, 247, 143, 203, 117, 2, 17, 0, 0, 0, 174, 10, 202, 113, 115, 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