Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0646f97e718e81bf36f68ea78ffc10810ea4babf97fcbe8d8de6c7d79548cfe4

Tx prefix hash: 1a04290e46d640fccdfcbe67eabcaa3d5b3a4ca1699347e07179f106f707ccd2
Tx public key: eeea7ae9ab41a0e5435f294bf0018e85fc14607966662907d238d7e90b907404
Timestamp: 1685966083 Timestamp [UCT]: 2023-06-05 11:54:43 Age [y:d:h:m:s]: 01:353:08:35:00
Block: 775645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513777 RingCT/type: yes/0
Extra: 01eeea7ae9ab41a0e5435f294bf0018e85fc14607966662907d238d7e90b9074040211000000014b8f5122000000000000000000

1 output(s) for total of 1.651833597000 dcy

stealth address amount amount idx
00: e6c2f9e50d3549362c84fd5b13f15bd0342df6a4410e252d5c844d21b330776d 1.651833597000 1225166 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": 775655, "vin": [ { "gen": { "height": 775645 } } ], "vout": [ { "amount": 1651833597, "target": { "key": "e6c2f9e50d3549362c84fd5b13f15bd0342df6a4410e252d5c844d21b330776d" } } ], "extra": [ 1, 238, 234, 122, 233, 171, 65, 160, 229, 67, 95, 41, 75, 240, 1, 142, 133, 252, 20, 96, 121, 102, 102, 41, 7, 210, 56, 215, 233, 11, 144, 116, 4, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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