Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f1fecea886373a2f477936c10a78e1a4954d481d7a3090ec0293719dd934b4e

Tx prefix hash: ae66fe782ae3d8a5c7b4537fe6b7c453644672a8acd7882be30364f9db8776bf
Tx public key: 0e1ab81b5d2acfca24caa23f6d76c36e35d06a2ff762a2ba96b6f32662aca9b0
Timestamp: 1583904011 Timestamp [UCT]: 2020-03-11 05:20:11 Age [y:d:h:m:s]: 04:302:03:04:54
Block: 80284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111055 RingCT/type: yes/0
Extra: 010e1ab81b5d2acfca24caa23f6d76c36e35d06a2ff762a2ba96b6f32662aca9b0021100000024d81c26c0000000000000000000

1 output(s) for total of 332.655006426000 dcy

stealth address amount amount idx
00: 7e1e159621431c31fc1f4093c06886ee6d5f3e32f28f17d9ccadd35567737d2c 332.655006426000 146956 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": 80294, "vin": [ { "gen": { "height": 80284 } } ], "vout": [ { "amount": 332655006426, "target": { "key": "7e1e159621431c31fc1f4093c06886ee6d5f3e32f28f17d9ccadd35567737d2c" } } ], "extra": [ 1, 14, 26, 184, 27, 93, 42, 207, 202, 36, 202, 162, 63, 109, 118, 195, 110, 53, 208, 106, 47, 247, 98, 162, 186, 150, 182, 243, 38, 98, 172, 169, 176, 2, 17, 0, 0, 0, 36, 216, 28, 38, 192, 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