Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a670c883b92d9c9c40306b4c331939a231e5f8d5d833204afe1e57c0dd484a0

Tx prefix hash: f6a6bb9fdc90eea2d500c46400d988323e20b3e0c5ccf3002088b9253c05be77
Tx public key: af2adbc7fb6e750edf8cccc889e85287ee62552366f4995a2442720fb33f9245
Timestamp: 1725779507 Timestamp [UCT]: 2024-09-08 07:11:47 Age [y:d:h:m:s]: 00:212:23:46:06
Block: 1105466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152068 RingCT/type: yes/0
Extra: 01af2adbc7fb6e750edf8cccc889e85287ee62552366f4995a2442720fb33f9245021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eab5e8e6472d1f48d344fd5f421f580a5bdfc00936d08d40fa68844ddc9fa21 0.600000000000 1582809 of 15

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": 1105476, "vin": [ { "gen": { "height": 1105466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eab5e8e6472d1f48d344fd5f421f580a5bdfc00936d08d40fa68844ddc9fa21" } } ], "extra": [ 1, 175, 42, 219, 199, 251, 110, 117, 14, 223, 140, 204, 200, 137, 232, 82, 135, 238, 98, 85, 35, 102, 244, 153, 90, 36, 66, 114, 15, 179, 63, 146, 69, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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