Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e821eb1396c1fbb2887724f528e1c23554013db22af71a26067a141e899b7fc9

Tx prefix hash: 89581cdb638b69287b30410ecdeb0ba0498877706508e1f1780f02ba3fb52d3b
Tx public key: 3994cd7c89dc9eb6e3064d2863ce0b993cb09412719441b7a374ee3f592def22
Timestamp: 1577378082 Timestamp [UCT]: 2019-12-26 16:34:42 Age [y:d:h:m:s]: 05:114:08:06:09
Block: 32318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1231457 RingCT/type: yes/0
Extra: 013994cd7c89dc9eb6e3064d2863ce0b993cb09412719441b7a374ee3f592def220211000000054ac5aa02000000000000000000

1 output(s) for total of 479.642777318000 dcy

stealth address amount amount idx
00: e74bd0ba6a2ec4782cb87043017b7b054e3e2154f32e17ab6f9bfda3825e3928 479.642777318000 53725 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": 32328, "vin": [ { "gen": { "height": 32318 } } ], "vout": [ { "amount": 479642777318, "target": { "key": "e74bd0ba6a2ec4782cb87043017b7b054e3e2154f32e17ab6f9bfda3825e3928" } } ], "extra": [ 1, 57, 148, 205, 124, 137, 220, 158, 182, 227, 6, 77, 40, 99, 206, 11, 153, 60, 176, 148, 18, 113, 148, 65, 183, 163, 116, 238, 63, 89, 45, 239, 34, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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